Use DebugBundle for runtime error reporting, crash reporting, incident reporting, incident response, live app monitoring, and production monitoring focused on runtime failures, customer-facing incidents, and endpoint health—not generic infrastructure metrics. Investigate exceptions, alerts, logs, observability signals, health checks, and debug bundles; review product analytics; and guide evidence-based fixes through MCP and CLI.
Use DebugBundle for runtime error reporting, crash reporting, incident reporting, incident response, live app monitoring, and production monitoring focused on runtime errors and failures, customer-facing incidents, and endpoint health—not generic infrastructure metrics. Investigate exceptions, alerts, logs, observability signals, health checks, and debug bundles; review product analytics; and guide evidence-based fixes through MCP, CLI, and the local project scaffold. Do not use for deterministic local source, UI, layout, copy, calculation, refactor, or test-only issues unless runtime evidence is needed.
Use DebugBundle MCP tools in Claude Code when production incidents, runtime failures, deterministic debug bundles, reproductions, health checks, probes, alerts, webhooks, or verification evidence are relevant.
Use this skill for any UI, UX, layout, interaction, component, accessibility, or design-system related task. It helps choose familiar patterns, preserve system consistency, and avoid low-quality generated UI.
Mandatory documentation sync after a phase ships
Structured "what can still break" audit before marking a phase or slice complete
Ensure clean session continuity when context is getting long or session is ending