Files
broesmel 87d3604a04 Wire mattpocock skills into engineering docs, fix stale misc README
Adds the 8 already-copied engineering skills (ask-matt, codebase-design,
domain-modeling, implement, prototype, resolving-merge-conflicts,
setup-matt-pocock-skills, triage) plus frontend-design to
engineering/README.md and plugin.json. Also rewrites misc/README.md,
which listed 3 skills with no matching folder and was missing 3 real ones.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-02 23:17:48 +02:00
..

Engineering

Skills I use daily for code work.

User-invoked

Reachable only when you type them (disable-model-invocation: true).

  • 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

Model- or user-reachable (rich trigger phrasing so the model can reach for them).

  • 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.