Troubleshoot App
Live UI / data-plane breakage; reproduce, isolate, evidence.
What it is
Section titled “What it is”Live UI / data-plane breakage; reproduce, isolate, evidence. This practice is a skill-mapped TTP: when, why, and which command—not a full copy of the skill. Open the skill to execute.
Why it works
Section titled “Why it works”Live incidents: reproduce → isolate → evidence before fix (SRE). This is the interactive product diagnosis cut (Quality regimes B) — pair with diagnose-bug for backend/algo (A) and agents analyze / Langfuse for generative (C). Prefer the quality trace over a private oracle; broken UX/framing still counts as a bug.
When to use it
Section titled “When to use it”When the situation matches the one-liner above and Orientation (or your project path) says this is the fire to touch now.
- Invoke the skill; follow its safety rules
- Keep one write owner; collect evidence before claiming done
- Hand off to the next practice instead of boiling the ocean
- Skip orientation when you’re lost
- Spawn overlapping agents to “go faster”
- Treat the practice as done without evidence
Related concepts
Section titled “Related concepts”04-evidence-over-vibes, 01-this-is-fine-stance, 11-quality-regimes, 12-bugs-and-debt, 13-quality-trace
Further reading
Section titled “Further reading”- Quality regimes (handbook)
- Google SRE — Managing incidents
- Google SRE — Four golden signals
- web.dev — Web Vitals
See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”troubleshoot-app