If you've ever caught yourself thinking "AI coding tools are great, but I'm doing the same prompt setup again and again," you'll want to look at what Matt Pocock just shipped.
The Total TypeScript founder open-sourced his personal .claude/skills/ folder on 2026-02-03. Three months later: 30,344 stars, 2,380 forks, still actively pushed. No marketing campaign. No launch post. Just a directory dump that resonated.
The repo is called, simply, mattpocock/skills. The slogan in the README is the whole thesis:
"My agent skills that I use every day to do real engineering — not vibe coding."
That distinction — real engineering vs vibe coding — is doing a lot of work. Let's unpack it.
Skills aren't prompts
Most people use AI coding tools by writing prompts. The better the prompt, the better the output. Matt's framing is different.
A skill is a process. It tells the AI how to work, not what to say. Same input, different process, fundamentally different output. Think of it less like writing a message to the AI and more like designing the workshop the AI lives in.
Let's see what that looks like in practice.
The 16 skills, by category
Planning & Design (5)
| Skill | What it does |
|---|---|
to-prd |
Synthesizes the current conversation into a PRD, files it as a GitHub issue. No interview — just synthesis of what's already been discussed. |
to-issues |
Breaks PRDs/specs into independent vertical-slice GitHub issues. |
grill-me |
Interrogates you until every branch of the decision tree is resolved. |
design-an-interface |
Uses parallel sub-agents to generate radically different interface designs. |
request-refactor-plan |
Interview → small-commit refactor plan → GitHub issue. |
The standout here is grill-me. It's like having a skeptical tech lead permanently stationed in your terminal. Why are you doing this now? What's the cost of this decision? What edge case haven't you considered? It won't shut up until you've answered everything. It's exhausting in the best possible way.
Development (5)
| Skill | What it does |
|---|---|
tdd |
Red-Green-Refactor loop, vertical slice at a time. |
triage-issue |
Explore codebase → root cause → TDD fix plan as issue. |
improve-codebase-architecture |
Finds deepening opportunities from CONTEXT.md + docs/adr/. |
migrate-to-shoehorn |
Migrates as assertions in tests to @total-typescript/shoehorn. |
scaffold-exercises |
Generates exercise directory structure. |
tdd is brilliant. Before any code is written, it forces 3 questions:
- Is this code designed to be testable?
- What is the core behavior?
- Does this require an interface change?
Notice where the friction is. It's not "before every action." It's "before code-writing — the place where rushing produces bad outcomes." You buckle the seatbelt where the road is dangerous, not where it's flat.
Tooling & Setup (2)
| Skill | What it does |
|---|---|
setup-pre-commit |
Husky + lint-staged + Prettier + typecheck + tests. |
git-guardrails-claude-code |
Blocks dangerous git commands at the hook level. |
git-guardrails-claude-code is the safety harness for autonomous loops. It blocks git push --force, git reset --hard, git clean -fd, etc. at the Claude Code hook layer — so your AI literally cannot nuke main at 3am.
Writing & Knowledge (4)
| Skill | What it does |
|---|---|
write-a-skill |
Generates new skills with progressive disclosure structure. |
edit-article |
Restructures sections, improves clarity, compresses prose. |
ubiquitous-language |
Extracts DDD ubiquitous language glossary from current conversation. |
obsidian-vault |
Manages Obsidian vault with wikilinks and index notes. |
write-a-skill is the meta layer. Skills that make skills. This is why the repo doesn't get stale: any user can fork it, run write-a-skill, and add their own workflow. The system extends itself.
Installation
The repo uses vercel-labs/skills (582K weekly downloads on npm):
# Install one skill in current project
npx skills@latest add mattpocock/skills/tdd
# Install globally (~/.claude/skills/)
npx skills add mattpocock/skills/tdd -g
# Install all 16 at once
npx skills add mattpocock/skills --all
Compatible with 49+ agents: Claude Code, Codex, Cursor, OpenCode, Gemini CLI, GitHub Copilot, OpenClaw, Antigravity, and more.
The four design principles
If you read the SKILL.md files across the 16 skills, four principles repeat:
1. Process > Prompt
The skill defines the workflow. The prompt is just a trigger.
2. Progressive Disclosure
Each SKILL.md root is under 50 lines. Detail goes into references/. The AI loads detail only when needed. This saves context tokens and keeps the surface area readable.
3. Vertical Slice
Every workflow that could be horizontal (TDD, refactoring, issue breakdown) is sliced vertically instead. One full feature end-to-end, then the next.
4. Self-extending
write-a-skill is itself a skill. The system extends itself. This is the secret sauce of the 30K stars — adoption snowballs because users add to the library.
What's the "Skill Economy"?
Vibe Sparking coined the phrase. The trajectory looks like this:
2025: Prompt engineering (individual know-how)
↓
2026 Q1: AGENTS.md / CLAUDE.md (project-level context)
↓
2026 Q2: Agent Skills (reusable workflows)
↓
2026+: Skill registry (npm-like ecosystem)
Two months ago, your AI workflow was implicit knowledge in your prompt. Today, it's a versioned artifact you can fork, share, and review. That's a fundamental change.
Matt also released a course in April 2026 — "Claude Code for Real Engineers" — covering Plan/Execute/Clear workflows, AGENTS.md patterns, and Ralph Wiggum autonomous loops. The skills repo is the practical foundation of that course.
Where to start (5 skills, 30 minutes)
If you're new to this, install these five and you'll see the difference within a week:
npx skills add mattpocock/skills/tdd -g
npx skills add mattpocock/skills/grill-me -g
npx skills add mattpocock/skills/to-prd -g
npx skills add mattpocock/skills/write-a-skill -g
npx skills add mattpocock/skills/git-guardrails-claude-code -g
Workflow examples:
- New feature:
grill-me→to-prd→tdd(withgit-guardrails-claude-coderunning quietly in the background) - Custom workflow:
write-a-skill→ share the skill with your team or open-source it back
Closing thoughts
The shift here isn't about better tooling. It's about AI as a collaborator with defined processes, not AI as an oracle you prompt. That distinction is what 30K stars are voting on.
Try it for a week. The change will compound.
Source repo: github.com/mattpocock/skills
Top comments (0)