cc-bible

This skill should be used when debugging a bug, error message, or test failure — tracing root cause, generating and ranking hypotheses, or when stuck/looping and needing an escalating strategy (step back, compare plans, naive-first, ultrathink). Contains Shumer's 9-step framework and 4 escalating techniques for getting unstuck.

This skill should be used when planning implementation work before writing code — drafting a plan, reviewing one as a staff engineer, structuring unresolved questions and success criteria, comparing two competing approaches, or ordering phases by dependency and risk. Contains plan formats, evaluation criteria, and the two-plan comparison technique.

This skill should be used when rewriting a vague or imperative prompt into a declarative, exhaustive, verification-driven one — expanding scope, injecting test/lint/build verification commands, defining completion criteria, or auditing UI and cross-cutting changes for full coverage. Contains exhaustiveness rules, verification patterns, and anti-patterns to fix.

This skill should be used when practicing test-driven development — writing one failing test at a time through RED-GREEN-REFACTOR, designing testable interfaces, deciding what to mock versus what not to mock, or choosing between pass@k and pass^k test strategies. Contains vertical-slicing rules and testing anti-patterns to avoid.