By jaymie9019
Matt Pocock's daily skills for real engineering — grilling, domain modeling, tickets, TDD, diagnosis, prototyping.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
My agent skills that I use every day to do real engineering - not vibe coding.
Developing real applications is hard. Approaches like GSD, BMAD, and Spec-Kit try to help by owning the process. But while doing so, they take away your control and make bugs in the process hard to resolve.
These skills are designed to be small, easy to adapt, and composable. They work with any model. They're based on decades of engineering experience. Hack around with them. Make them your own. Enjoy.
If you want to keep up with changes to these skills, and any new ones I create, you can join ~60,000 other devs on my newsletter:
npx skills@latest add mattpocock/skills
Pick the skills you want, and which coding agents you want to install them on. Make sure you select /setup-matt-pocock-skills.
Run /setup-matt-pocock-skills in your agent. It will:
/triage uses labels)Bam - you're ready to go.
This repo is also a Claude Code plugin marketplace. Each bucket is a separately installable plugin, so you can grab just the category you want.
# Add the marketplace once
claude plugin marketplace add mattpocock/skills
# Then install whichever buckets you want
claude plugin install engineering@mattpocock-skills
claude plugin install productive@mattpocock-skills
claude plugin install misc@mattpocock-skills
claude plugin install personal@mattpocock-skills
Available plugins: engineering, productive, misc, personal. After installing engineering, run /setup-matt-pocock-skills once per repo as described above.
The same repo is also a Codex marketplace (it reuses the exact same skills). Each bucket is a separately installable Codex plugin.
# Add the marketplace once
codex plugin marketplace add mattpocock/skills
# Then install whichever buckets you want
codex plugin add engineering@mattpocock-skills
codex plugin add productive@mattpocock-skills
codex plugin add misc@mattpocock-skills
codex plugin add personal@mattpocock-skills
Both the Claude and Codex plugins ship the same skills for every bucket.
I built these skills as a way to fix common failure modes I see with Claude Code, Codex, and other coding agents.
"No-one knows exactly what they want"
David Thomas & Andrew Hunt, The Pragmatic Programmer
The Problem. The most common failure mode in software development is misalignment. You think the dev knows what you want. Then you see what they've built - and you realize it didn't understand you at all.
This is just the same in the AI age. There is a communication gap between you and the agent. The fix for this is a grilling session - getting the agent to ask you detailed questions about what you're building.
The Fix is to use:
/grill-me - for non-code uses/grill-with-docs - same as /grill-me, but adds more goodies (see below)These are my most popular skills. They help you align with the agent before you get started, and think deeply about the change you're making. Use them every time you want to make a change.
With a ubiquitous language, conversations among developers and expressions of the code are all derived from the same domain model.
Eric Evans, Domain-Driven-Design
The Problem: At the start of a project, devs and the people they're building the software for (the domain experts) are usually speaking different languages.
npx claudepluginhub jaymie9019/mattpocock-skills --plugin engineeringTools kept around but rarely used — git guardrails, shoehorn migration, exercise scaffolding, pre-commit setup.
Jaymie's personal toolbox of Claude Code skills
Daily non-code workflow tools — grilling, handoff, teaching, and writing great skills.
Skills tied to my own setup — editing articles and managing an Obsidian vault.
Ultra-compressed communication mode. Cuts 65% of output tokens (measured) while keeping full technical accuracy by speaking like a caveman.
Frontend design skill for UI/UX implementation
Memory compression system for Claude Code - persist context across sessions
Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.