mattpocock

38 skills

grill-memattpocock1.2MA relentless interview to sharpen a plan or design.grill-with-docsmattpocock1.1MA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.tddmattpocock979KTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.setup-matt-pocock-skillsmattpocock905KConfigure 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.handoffmattpocock883KCompact the current conversation into a handoff document for another agent to pick up.triagemattpocock854KMove issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.prototypemattpocock852KBuild 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.grillingmattpocock792KGrill 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.teachmattpocock724KTeach the user a new skill or concept, within this workspace.domain-modelingmattpocock714KBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.codebase-designmattpocock691KShared 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, or when another skill needs the deep-module vocabulary.diagnosing-bugsmattpocock678KDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".implementmattpocock627KImplement a piece of work based on a spec or set of tickets.ask-mattmattpocock626KAsk which skill or flow fits your situation. A router over the skills in this repo.wayfindermattpocock579KPlan 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.to-specmattpocock576KTurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.researchmattpocock575KInvestigate 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.to-ticketsmattpocock566KBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).resolving-merge-conflictsmattpocock552KUse when you need to resolve an in-progress git merge/rebase conflict.wizardmattpocock424KGenerate 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. Don't invoke this for steps the agent can perform itself.git-guardrails-claude-codemattpocock408KSet 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/reset in Claude Code.setup-pre-commitmattpocock399KSet 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/testing.writing-beatsmattpocock393KWriting, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.writing-shapemattpocock392KWriting, exploit: shape raw material into an article, paragraph by paragraph.scaffold-exercisesmattpocock392KCreate 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.writing-fragmentsmattpocock392KWriting, explore: mine raw fragments, no structure yet.migrate-to-shoehornmattpocock388KMigrate 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.to-questionnairemattpocock374KTurn a decision you can't fully answer into a questionnaire for someone else to fill in.loop-memattpocock348KGrill me about specs for the workflows I want to build, within this workspace.writing-for-agentsmattpocock330KWriting documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.claude-handoffmattpocock324KHand the current conversation off to a fresh background agent that picks up the work immediately.wait-whatmattpocock315KStop. That last message did not land: re-pitch it.setup-ts-deep-modulesmattpocock279KWire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.implement-specmattpocock154KImplement a specification in code.retromattpocock141KConduct a retrospective on a coding session.prmattpocock39KUse when writing a PR body.