dev-config/README.md

Skills

Personal Claude Code skills, organized into bucket folders under skills/. See CLAUDE.md for the rules that keep this index in sync with the skill folders and for the User-invoked vs Model-invoked split.

Engineering

Skills I use daily for code work.

User-invoked

• ask-matt — Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
• grill-with-docs — Grilling session that also builds your project's domain model, sharpening terminology and updating CONTEXT.md and ADRs inline.
• triage — Move issues through a state machine of triage roles.
• improve-codebase-architecture — Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
• setup-matt-pocock-skills — Configure this repo for the engineering skills (issue tracker, triage labels, domain doc layout). Run once per repo.
• to-issues — Break any plan, spec, or PRD into independently-grabbable issues using vertical slices.
• to-prd — Turn the current conversation into a PRD and publish it to the issue tracker.
• prototype — Build a throwaway prototype — a runnable terminal app for state/logic questions, or several toggleable UI variations.
• implement — Implement work from a PRD or set of issues: TDD at pre-agreed seams, typecheck and test as you go, then review and commit.

Model-invoked

• diagnosing-bugs — Disciplined diagnosis loop for hard bugs and performance regressions: reproduce → minimise → hypothesise → instrument → fix → regression-test.
• tdd — Test-driven development with a red-green-refactor loop. Builds features or fixes bugs one vertical slice at a time.
• domain-modeling — Actively build and sharpen a project's domain model — challenge terms, stress-test with scenarios, update CONTEXT.md and ADRs inline.
• codebase-design — Shared discipline and vocabulary for designing deep modules: small interfaces, clean seams, testable through the interface.
• resolving-merge-conflicts — Work an in-progress git merge/rebase conflict hunk by hunk, resolving by intent, and always finish it (never --abort).
• frontend-design — Build distinctive, production-grade frontend UI that avoids generic "AI slop" aesthetics.

Productivity

Daily non-code workflow tools.

User-invoked

• grill-me — Relentless interview to sharpen a plan or design, for non-code uses.
• handoff — Compact the current conversation into a handoff document so another agent can continue the work.

Model-invoked

• grilling — Interview the user relentlessly about a plan or design until every branch of the decision tree is resolved. The reusable loop behind grill-me.

Misc

Tools I keep around but rarely use.

Model-invoked

• codex-debugging — Investigate Codex CLI/app-server behavior, config parsing, tool behavior, prompts, and MCP wiring bugs.
• git-guardrails-claude-code — Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.
• github-deep-review — Evidence-first review of a bug or PR: read the code, find the real cause, decide the best fix, and say "not proven" when the trail is weak.
• github-project-triage — Triage a GitHub project's issues/PRs into maintainer-facing item cards: what it's about, risk, proof/test state, blockers, next action.