Matt Pocock skills

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions red-green-refactor, or wants integration tests.

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Move issues and external PRs through a state machine of triage roles: categorise, verify, grill if needed, and write agent-ready briefs.

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable.

Diagnosis loop for hard bugs and performance regressions. Use when the user says diagnose or debug this, or reports something broken, throwing, failing, or slow.

Review the changes since a fixed point along two axes: Standards and Spec. Runs both reviews in parallel sub-agents and reports them side by side.

Implement a piece of work based on a spec or set of tickets.

Ask which skill or flow fits your situation. A router over the skills in this repo.

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Turn the current conversation into a spec and publish it to the project issue tracker. No interview, just synthesis of what you've already discussed.

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker.

Use when you need to resolve an in-progress git merge or rebase conflict.

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover.

A relentless interview to sharpen a plan or design.

Compact the current conversation into a handoff document for another agent to pick up.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any grill trigger phrases.

Teach the user a new skill or concept, within this workspace.

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Stop. That last message did not land. Re-pitch it.

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push or reset in Claude Code.

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting, typechecking, or testing.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.