systematic-debugging
Systematic Debugging
Overview
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Violating the letter of this process is violating the spirit of debugging.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
When to Use
More from jtsang4/efficient-coding
brainstorming
Use only when the user explicitly asks to do brainstorming (e.g., says 'brainstorm'/'头脑风暴' or invokes $brainstorming). Do not auto-trigger based on general creative work.
17writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
16dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
13subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
13executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
12shape
>
11