debug▌

Largest Contentful Paint (LCP) measures how quickly a page's main content becomes visible. It's the time from navigation start until the largest image or text block renders in the viewport.

Comprehensive Vue 3 debugging reference covering reactivity, components, templates, lifecycle, SSR, and 100+ common runtime issues. \n \n Organized by feature area (reactivity, computed, watchers, components, templates, forms, lifecycle, SSR, TypeScript, and more) with direct links to specific error scenarios and fixes \n Covers Vue 3 specific gotchas including ref unwrapping, proxy identity hazards, v-model composition events, template ref timing, and hydration mismatches \n Addresses async pat

Keep this workflow focused on existing debug windows and menu entries. Do not add a new utility/debug control window unless the user asks explicitly.

Comprehensive Vue 3 debugging reference covering reactivity, components, templates, lifecycle, SSR, and 100+ common runtime issues. \n \n Organized by feature area (reactivity, computed, watchers, components, templates, forms, lifecycle, SSR, TypeScript, animations, and more) with direct links to specific error scenarios and fixes \n Covers Vue 3 specific gotchas including ref unwrapping, proxy identity hazards, v-model IME composition, template ref timing, and hydration mismatches \n Addresses

Debug logging utility with namespace-based filtering across desktop, server, and client environments. \n \n Follows strict namespace conventions (e.g., lobe-server:[module] , lobe-desktop:[module] ) to organize logs by platform and module \n Supports format specifiers including %O for expanded objects, %s for strings, and %d for numbers \n Enable output via localStorage.debug in browsers, DEBUG environment variable in Node.js, or process.env.DEBUG in Electron \n Wildcard filtering (e.g., lobe-*

elixir/docs/logging.md requires these fields for issue/session lifecycle logs. Use them as your join keys during debugging.

Comprehensive debugging methodology guide for software engineers, containing 54 rules across 10 categories prioritized by impact. Based on research from Andreas Zeller's "Why Programs Fail" and academic debugging curricula.

Status: Production Ready Last Updated: 2026-02-03 Dependencies: Chrome MCP tools (optional), debugger agent, code-reviewer agent

You are an expert AI-assisted debugging specialist with deep knowledge of modern debugging tools, observability platforms, and automated root cause analysis.

You are an expert AI-assisted debugging specialist with deep knowledge of modern debugging tools, observability platforms, and automated root cause analysis.