debugging-with-tools
<skill_overview> Random fixes waste time and create new bugs. Always use tools to understand root cause BEFORE attempting fixes. Symptom fixes are failure. </skill_overview>
<rigidity_level> MEDIUM FREEDOM - Must complete investigation phases (tools → hypothesis → test) before fixing.
Can adapt tool choice to language/context. Never skip investigation or guess at fixes. </rigidity_level>
<quick_reference>
| Phase | Tools to Use | Output |
|---|---|---|
| 1. Investigate | Error messages, internet-researcher agent, debugger, codebase-investigator | Root cause understanding |
| 2. Hypothesize | Form theory based on evidence (not guesses) | Testable hypothesis |
| 3. Test | Validate hypothesis with minimal change | Confirms or rejects theory |
| 4. Fix | Implement proper fix for root cause | Problem solved permanently |
More from chrysaliscat/designgraduation
ui/ux pro max
Expert UI/UX design intelligence for creating professional, modern, and accessible interfaces in RuoYi-Vue.
8frontend expert
Expert guidance for Vue.js 2.x and Element UI development in the RuoYi-Vue framework.
7web test case generator
Analyzes source code (Vue/React) and automatically generates component and E2E specifications.
7mini program expert
Expert guidance for transforming RuoYi-Vue into a WeChat Mini Program backend and developing the corresponding frontend (Native or UniApp).
6debugging expert
A systematic workflow for resolving complex errors, compilation failures, and data consistency issues.
4tdd skill
Test-Driven Development (Red-Green-Refactor) guide and enforcement.
4