Files
skills/skills/engineering
Matt PocockandClaude Opus 4.8 43ea0884b0 tdd: add tautological-test anti-pattern
Tests whose assertion is recomputed the way the code computes it pass by
construction and give zero confidence. Add it as a peer of the existing
implementation-coupling anti-pattern: a Philosophy principle, a per-cycle
checklist gate, and a BAD/GOOD example pair in tests.md. Includes a patch
changeset.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-29 21:22:50 +01:00
..
2026-06-12 09:25:19 +01:00
2026-06-12 09:25:19 +01:00
2026-06-18 09:41:30 +01: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.

Model-invoked

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

  • prototype — Build a throwaway prototype to answer a design question: a runnable terminal app for state/logic, or several toggleable UI variations.

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