Four-phase debugging: root cause → patterns → hypothesis → implement. For complex bugs, test failures, multi-component issues. NOT for obvious syntax errors.
Uses a four-phase method (root cause → patterns → hypothesis → implement) to debug complex bugs, test failures, and multi-component issues. Triggers when investigating technical problems instead of applying quick fixes.
/plugin marketplace add jrc1883/popkit-claude/plugin install popkit-ops@popkit-claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Random fixes waste time. Quick patches mask issues.
Core principle: ALWAYS find root cause before fixes. Symptom fixes are failure.
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION
ANY technical issue: test failures, bugs, unexpected behavior, performance, builds, integration.
ESPECIALLY when:
Don't skip when:
For test failures, check flakiness FIRST:
Test fails → Run 5x
├─ Passes 5/5: Not flaky, investigate as bug
├─ Fails 5/5: Consistent, investigate as bug
└─ Mixed (3/5): FLAKY TEST - fix test first
Flaky test checklist:
| Check | How | Fix |
|---|---|---|
| Isolated/connected? | Run single vs suite | State pollution |
| Timing-dependent? | Look for timeouts/sleeps | Condition-based waiting |
| Environment-specific? | CI vs local | Mock env vars |
| Order-dependent? | Different order | Setup/teardown |
| Race condition? | Async without waits | Proper async/await |
Then continue:
Create Failing Test - Use test-driven-development skill
Implement Single Fix - Address root cause, ONE change
Verify Fix - Test passes, no other tests broken
If Fix Doesn't Work
If 3+ Fixes Failed: Question Architecture
STOP if thinking:
ALL → Return to Phase 1
3+ failures → Question architecture
| Phase | Key Activities | Success |
|---|---|---|
| 1. Root Cause | Read errors, reproduce, gather evidence | Understand WHAT & WHY |
| 2. Pattern | Find working examples, compare | Identify differences |
| 3. Hypothesis | Form theory, test minimally | Confirmed or new |
| 4. Implement | Test, fix, verify | Resolved, tests pass |
See examples/ for:
flaky-test-patterns.md - Common flaky test causes & fixesdebugging-flowchart.pdf - Visual decision treemulti-component-diagnostic.md - Instrumentation strategyCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.