원클릭으로
debug-mastery
// Systematic debugging methodology with 4-phase process, root cause tracing, and elite observability standards. No fixes without investigation.
// Systematic debugging methodology with 4-phase process, root cause tracing, and elite observability standards. No fixes without investigation.
| name | debug-mastery |
| description | Systematic debugging methodology with 4-phase process, root cause tracing, and elite observability standards. No fixes without investigation. |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
<domain_overview>
Philosophy: Random fixes waste time and create new bugs. Quick patches mask underlying issues. ALWAYS find root cause before attempting fixes. FORENSIC ANALYSIS MANDATE (CRITICAL): Never apply a fix without a confirmed root cause. AI-generated fixes often address symptoms rather than underlying architectural logic. You MUST perform a 'Forensic Investigation' that identifies the specific assumption or boundary condition that failed. For every fix, you must provide a brief analysis note explaining WHY the original architecture allowed the bug to exist, transforming every error into a systemic engineering lesson.
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Use for ANY technical issue:
You MUST complete each phase before proceeding to the next.
BEFORE attempting ANY fix:
For EACH component boundary:
- Log what data enters component
- Log what data exits component
- Verify environment/config propagation
- Check state at each layer
Run once to gather evidence showing WHERE it breaks
THEN analyze evidence to identify failing component
THEN investigate that specific component
@root-cause-tracing.md for the complete backward tracing technique.
Quick version:
Find the pattern before fixing:
Scientific method:
Fix the root cause, not the symptom:
@tdd-mastery skill for writing proper failing testsIf you catch yourself thinking:
| Excuse | Reality |
|---|---|
| "Issue is simple, don't need process" | Simple issues have root causes too. Process is fast for simple bugs. |
| "Emergency, no time for process" | Systematic debugging is FASTER than guess-and-check thrashing. |
| "Just try this first, then investigate" | First fix sets the pattern. Do it right from the start. |
| "I'll write test after confirming fix works" | Untested fixes don't stick. Test first proves it. |
| "Multiple fixes at once saves time" | Can't isolate what worked. Causes new bugs. |
| "Reference too long, I'll adapt the pattern" | Partial understanding guarantees bugs. Read it completely. |
| "I see the problem, let me fix it" | Seeing symptoms ≠ understanding root cause. |
| "One more fix attempt" (after 2+ failures) | 3+ failures = architectural problem. Question pattern, don't fix again. |
| </red_flags_and_rationalizations> | |
| <observability_and_references> |
| Phase | Key Activities | Success Criteria |
|---|---|---|
| 1. Root Cause | Read errors, reproduce, check changes, gather evidence | Understand WHAT and WHY |
| 2. Pattern | Find working examples, compare | Identify differences |
| 3. Hypothesis | Form theory, test minimally | Confirmed or new hypothesis |
| 4. Implementation | Create test, fix, verify | Bug resolved, tests pass |
These techniques are part of systematic debugging:
@root-cause-tracing.md - Trace bugs backward through call stack to find original trigger@defense-in-depth.md - Add validation at multiple layers after finding root causeMandatory Fields: timestamp, level, traceId, component, message, context
Log Levels:
TraceIDFrontend:
ux-audit.js for layout shifts
Backend:chrome.alarms pulsesFrom debugging sessions:
Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.
Elite Tier Backend standards, including Vertical Slice Architecture, Zero Trust Security, and High-Performance API protocols.
Design-first methodology. Explore user intent, requirements and design before implementation. Turn ideas into fully formed specs through collaborative dialogue.
Master specialized skill for building 2025/2026-grade browser extensions. Deep expertise in Manifest v3, Service Worker persistence (Alarms, Offscreen API), Side Panel API, and Cross-Browser compatibility.
The Foundation Skill. LLM Firewall + 2025 Security + Cross-Skill Coordination. Use for ALL code output - prevents hallucinations, enforces security, ensures quality.
Elite Tier Web UI standards, including pixel-perfect retro aesthetics, immersive layouts, and UX psychology protocols.