ddd-verify
Compare finished code against requirements and applicable official docs, research unexplained discrepancies, correct authorized changes, and run affected checks. Use for verification or review of an implementation.
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Compare finished code against requirements and applicable official docs, research unexplained discrepancies, correct authorized changes, and run affected checks. Use for verification or review of an implementation.
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Required Matt Pocock workflow entry for engineering research, planning, building, debugging and review when Matt is the selected methodology. Track ordered phases, coordinate authorized workers and require evidence. Matt owns engineering in every harness.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Grill 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.
Compact the current conversation into a handoff document for another agent to pick up.
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, del
A WCAG 2.2 AA audit of a file or URL with a code fix for every finding, and --fix to apply them. Use when a page or component needs to be checked for everyone, beyond what the contrast check sees.
Build a brand kit from one or two colours, a name or a URL: three directions rendered as real work, one picked, written to brand/ and .desk/DESIGN.md. Use when a project has no brand yet or needs a proper one.
One chart that answers one question, as an HTML file with an inline SVG, colourblind-safe, directly labelled, with the takeaway as the title. Use when you have data and a point to make with it.
The Desk Studio dashboard. See every desk, the job, the roughs and scores, and steer it: pause, change a model, write a desk a note, pick a rough, approve. setup, start, stop, status or disable.
A dashboard screen laid out from the decisions it serves: KPI row, charts, filter bar, table, sidebar, every state, at phone, tablet and desktop. Use when a product or a team needs a screen of numbers that reads.
Design anything with the full studio loop. Pages, components, cards, carousels, emails, decks, charts, clips, brand assets. Staffs the desks, runs roughs, pick, polish, proof and sign-off, hands back files with scores.
A heuristic critique of a screen or flow against the Nielsen ten usability heuristics plus the studio rubric, from a screenshot, a file or a URL. Use when you want a usability read, not a redesign.
Turn a finished job into what an engineer needs: tokens, redline specs, component API docs and the asset list. Use after a job is signed off and someone else will build it in the product.
QA a built screen or component at three breakpoints for token compliance, every state and its motion, with a fix list. Use before a UI change ships, or when a page looks off and nobody can say why.
Catalog captured:2026-11-21