- Introduced a human-in-the-loop script for bug diagnosis to capture user feedback. - Created ADR and CONTEXT formats to standardize architectural decision records and domain context documentation. - Developed a domain modeling skill to refine terminology and maintain a shared language. - Enhanced the improve-codebase-architecture skill to provide visual reports and deepening opportunities. - Consolidated grilling and handoff skills for better user interaction and documentation. - Updated existing skills to improve clarity and consistency in descriptions and functionality.
2.1 KiB
2.1 KiB
Engineering
Skills I use daily for code work.
Commands
User-invoked entry points (disable-model-invocation: true).
- grill-with-docs — Grilling session that also builds your project's domain model, sharpening terminology and updating
CONTEXT.mdand 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.
- zoom-out — Ask the agent to zoom out a level and map the relevant modules and callers.
- prototype — Build a throwaway prototype — a runnable terminal app for state/logic questions, or several toggleable UI variations.
Skills
Model- or user-invocable (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.mdand ADRs inline. - codebase-design — Shared discipline and vocabulary for designing deep modules: small interfaces, clean seams, testable through the interface.