From shipshitdev-library
Provides 54-rule debugging methodology across 10 categories for bug reproduction, hypothesis-driven investigation, root cause analysis, and verification. Use for errors, crashes, stack traces, or incidents.
npx claudepluginhub shipshitdev/skillsThis skill uses the workspace's default tool permissions.
Comprehensive debugging methodology guide for software engineers, containing 54 rules across 10 categories prioritized by impact. Based on research from Andreas Zeller's "Why Programs Fail" and academic debugging curricula.
AGENTS.mdREADME.mdassets/templates/_template.mdreferences/_sections.mdreferences/anti-blame-tool.mdreferences/anti-debug-fatigue.mdreferences/anti-quick-patch.mdreferences/anti-shotgun-debugging.mdreferences/anti-tunnel-vision.mdreferences/hypo-binary-search.mdreferences/hypo-one-change-at-time.mdreferences/hypo-rubber-duck.mdreferences/hypo-rule-out-obvious.mdreferences/hypo-scientific-method.mdreferences/hypo-where-not-what.mdreferences/obs-breakpoint-strategy.mdreferences/obs-log-inputs-outputs.mdreferences/obs-stack-trace-reading.mdreferences/obs-strategic-logging.mdreferences/obs-trace-data-flow.mdProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Comprehensive debugging methodology guide for software engineers, containing 54 rules across 10 categories prioritized by impact. Based on research from Andreas Zeller's "Why Programs Fail" and academic debugging curricula.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Problem Definition | CRITICAL | prob- |
| 2 | Hypothesis-Driven Search | CRITICAL | hypo- |
| 3 | Observation Techniques | HIGH | obs- |
| 4 | Root Cause Analysis | HIGH | rca- |
| 5 | Tool Mastery | MEDIUM-HIGH | tool- |
| 6 | Bug Triage and Classification | MEDIUM | triage- |
| 7 | Common Bug Patterns | MEDIUM | pattern- |
| 8 | Fix Verification | MEDIUM | verify- |
| 9 | Anti-Patterns | MEDIUM | anti- |
| 10 | Prevention & Learning | LOW-MEDIUM | prev- |
prob-reproduce-before-debug - Reproduce the bug before investigatingprob-minimal-reproduction - Create minimal reproduction casesprob-document-symptoms - Document symptoms preciselyprob-separate-symptoms-causes - Separate symptoms from causesprob-state-expected-actual - State expected vs actual behaviorprob-recent-changes - Check recent changes firsthypo-scientific-method - Apply the scientific methodhypo-binary-search - Use binary search to localize bugshypo-one-change-at-time - Test one hypothesis at a timehypo-where-not-what - Find WHERE before asking WHAThypo-rule-out-obvious - Rule out obvious causes firsthypo-rubber-duck - Explain the problem aloudobs-strategic-logging - Use strategic loggingobs-log-inputs-outputs - Log function inputs and outputsobs-breakpoint-strategy - Use breakpoints strategicallyobs-stack-trace-reading - Read stack traces bottom to topobs-watch-expressions - Use watch expressions for stateobs-trace-data-flow - Trace data flow through systemrca-five-whys - Use the 5 Whys techniquerca-fault-propagation - Trace fault propagation chainsrca-last-known-good - Find the last known good staterca-question-assumptions - Question your assumptionsrca-examine-boundaries - Examine system boundariestool-conditional-breakpoints - Use conditional breakpointstool-logpoints - Use logpoints instead of modifying codetool-step-commands - Master step over/into/outtool-call-stack-navigation - Navigate the call stacktool-memory-inspection - Inspect memory and object statetool-exception-breakpoints - Use exception breakpointstriage-severity-vs-priority - Separate severity from prioritytriage-user-impact-assessment - Assess user impact before prioritizingtriage-reproducibility-matters - Factor reproducibility into triagetriage-quick-wins-first - Identify and ship quick wins firsttriage-duplicate-detection - Detect and link duplicate bug reportspattern-null-pointer - Recognize null pointer patternspattern-off-by-one - Spot off-by-one errorspattern-race-condition - Identify race condition symptomspattern-memory-leak - Detect memory leak patternspattern-type-coercion - Watch for type coercion bugspattern-async-await-errors - Catch async/await error handling mistakespattern-timezone-issues - Recognize timezone and date bugsverify-reproduce-fix - Verify with original reproductionverify-regression-check - Check for regressionsverify-understand-why-fix-works - Understand why fix worksverify-add-test - Add test to prevent recurrenceanti-shotgun-debugging - Avoid shotgun debugginganti-quick-patch - Avoid quick patches without understandinganti-tunnel-vision - Avoid tunnel vision on initial hypothesisanti-debug-fatigue - Recognize debugging fatigueanti-blame-tool - Don't blame the tool too quicklyprev-document-solution - Document bug solutionsprev-postmortem - Conduct blameless postmortemsprev-defensive-coding - Add defensive code at boundariesprev-improve-error-messages - Improve error messagesRead individual reference files for detailed explanations and code examples:
For the complete guide with all rules expanded: AGENTS.md