Walks you through reading an unfamiliar codebase instead of summarizing it for you. Presents a map, then guides you component by component while you read the code, predict what it does, and build your own working model.
1 skill
Guides you through diagnosing and fixing a bug yourself instead of patching it for you. Gathers the evidence, poses ranked hypotheses, and walks the investigation one step at a time while you form the diagnosis and write the fix.
1 skill
Stress-tests your system design decisions instead of producing an architecture for you. Interviews you about constraints, poses one trade-off at a time, and challenges each decision you make with concrete failure scenarios.
1 skill
Guides you through writing your own technical document instead of generating one for you. Covers design docs, RFCs, ADRs, runbooks, postmortems, specs, PRDs, proposals (change proposals included), one-pagers, project plans and briefs, READMEs, and more.
1 skill
Guides you through estimating your own work instead of producing estimates for you. Maps what each ticket actually touches — hidden work, unknowns, and how AI-assisted coding reshapes the effort — then you name every estimate and defend it against concrete stress tests. Ends with an estimate sheet verified against your words and sources.
1 skill
Guides you through decomposing a coding project into an execution plan you own instead of generating a plan for you. Mines your docs, tickets, and codebase for the real work and dependencies while you make every scoping, sequencing, and milestone decision — ending with an outline of steps, milestones, and tickets, verified claim by claim against your sources, plus a handoff to doc-coach for the shareable writeup.
1 skill
Interactive companion that guides you through manually reviewing someone else's pull request instead of reviewing it for you. Explains the PR's scope, breaks the change into logical components, and walks through them one at a time while you form your own judgment.
1 skill
Guides you through reading a paper or long document instead of summarizing it for you. Maps the structure, tells you which sections carry the substance, and checks your takeaways against the text while you do the reading.
1 skill
Guides you through running a technical spike or experiment yourself instead of handing you a conclusion. You frame the unknown, the decision it unblocks, and what result would kill the hypothesis; Claude builds and runs the throwaway experiment and reports observations with evidence; you interpret the results and state a verdict checked against what actually ran.
1 skill
Helps you decide what to test instead of generating a test suite for you. Maps the code's risk surface and asks what behavior you would protect and what input breaks it. You name the cases, then write them yourself or approve specific ones for Claude to implement.
1 skill