/debug - Systematic Problem Investigation
$ARGUMENTS
Purpose
This command activates DEBUG mode for systematic investigation of issues, errors, or unexpected behavior.
Behavior
When /debug is triggered:
- •
Gather information
- •Error message
- •Reproduction steps
- •Expected vs actual behavior
- •Recent changes
- •
Form hypotheses
- •List possible causes
- •Order by likelihood
- •
Investigate systematically
- •Test each hypothesis
- •Check logs, data flow
- •Use elimination method
- •
Fix and prevent
- •Apply fix
- •Explain root cause
- •Add prevention measures
Output Format
markdown
## 🔍 Debug: [Issue] ### 1. Symptom [What's happening] ### 2. Information Gathered - Error: `[error message]` - File: `[filepath]` - Line: [line number] ### 3. Hypotheses 1. ❓ [Most likely cause] 2. ❓ [Second possibility] 3. ❓ [Less likely cause] ### 4. Investigation **Testing hypothesis 1:** [What I checked] → [Result] **Testing hypothesis 2:** [What I checked] → [Result] ### 5. Root Cause 🎯 **[Explanation of why this happened]** ### 6. Fix ```[language] // Before [broken code] // After [fixed code]
7. Prevention
🛡️ [How to prevent this in the future]
code
--- ## Examples
/debug login not working /debug API returns 500 /debug form doesn't submit /debug data not saving
code
--- ## Key Principles - **Ask before assuming** - get full error context - **Test hypotheses** - don't guess randomly - **Explain why** - not just what to fix - **Prevent recurrence** - add tests, validation --- Built with ❤️ from [Antigravity Kit](https://github.com/vudovn/antigravity-kit) & UXUI ProMax MIT © Vudovn