Meta Description: Matt Pocock's "skills" repo hit 26K+ stars in days — a curated set of agent skills for planning, TDD, refactoring, and architecture. Here's what it means for real engineering workflows.
The Problem: AI Agents That Don't Think Like Engineers
Most AI coding assistants fall into the same trap. You describe what you want, and they immediately start writing code. No planning. No questioning. No validation. It's "vibe coding" — and it produces the kind of software that looks right but falls apart under pressure.
Matt Pocock — the TypeScript educator behind Total TypeScript — dropped an open-source repo this week that takes a fundamentally different approach. Called simply skills, it's a collection of reusable agent skills designed for real engineering, not casual code generation.
The repo gained over 26,000 stars in its first week. That's not hype — that's developers recognizing a missing layer in their AI workflows.
What Are Agent Skills?
If you've used Claude Code, you know about .claude directories — configuration files that shape how the AI agent behaves in your project. Skills take this further. They're self-contained instruction sets that give an AI agent a specific workflow, not just knowledge.
Think of it this way: a system prompt tells an agent what it knows. A skill tells an agent what to do — step by step, with guardrails, in a repeatable way.
Matt Pocock's collection targets the phases of development where most AI tools fall short: planning before code, structured refactoring, and disciplined testing.
The Planning & Design Skills (Think Before You Code)
This is where the collection shines brightest. These five skills force the agent to slow down and think:
to-prd — Takes your conversation context and synthesizes it into a proper Product Requirements Document, filed as a GitHub issue. No back-and-forth interview. The agent reads what you've already discussed and writes the spec.
to-issues — Breaks a PRD or plan into independently grabbable GitHub issues, sliced vertically (each one delivers user value on its own). This alone solves one of the biggest problems in AI-assisted development: the agent tries to do everything at once.
grill-me — The agent relentlessly interviews you about your plan or design. It doesn't stop until every branch of the decision tree is resolved. It's like having a senior engineer who won't let you merge until you've answered all the hard questions.
design-an-interface — Generates multiple radically different interface designs for a module using parallel sub-agents. Instead of the first idea that comes to mind, you get options to compare.
request-refactor-plan — Walks you through a refactor via interview, creates a detailed plan with tiny commits, and files it as a GitHub issue. The plan itself is valuable documentation.
The Development Skills (Code With Discipline)
Once planning is done, these skills enforce engineering best practices:
tdd — Test-driven development with a strict red-green-refactor loop. Features get built one vertical slice at a time. The agent writes a failing test, makes it pass, then refactors. This is how TDD is supposed to work, and most developers never do it manually. With an agent enforcing the loop, it actually happens.
triage-issue — When a bug comes in, the agent explores the codebase, identifies the root cause, and files a GitHub issue with a TDD-based fix plan. No more rubber-ducking a stack trace alone at 2 AM.
improve-codebase-architecture — The agent reads your
CONTEXT.mdanddocs/adr/(Architecture Decision Records) to find opportunities for deepening — making the codebase's structure better reflect its domain. It's like a periodic architecture review that actually produces action items.
Why This Matters for Engineering Teams
The real insight here isn't any single skill. It's the philosophy: AI agents should enforce process, not skip it.
Here's what that looks like in practice:
- You talk through an idea with your agent
- to-prd captures it as a proper spec
- grill-me stress-tests the spec
- to-issues breaks it into grabbable work items
- tdd implements each one with test-first discipline
- triage-issue handles bugs the same way
Every step has structure. Every step produces artifacts (GitHub issues, test files, PRs) that persist beyond the conversation. The agent isn't just writing code — it's participating in your engineering workflow.
Getting Started
Each skill installs with a single command:
npx skills@latest add mattpocock/skills/<skill-name>
They work with Claude Code out of the box. The npx skills CLI handles the setup — adding the skill's instructions to your .claude configuration.
If you're using other agent frameworks (like OpenClaw, Cursor, or Windsurf), the skills are just markdown files. You can read the source and adapt the patterns to your setup. The workflows are framework-agnostic; only the installation method changes.
The Bigger Picture: Agent Skills as Infrastructure
This repo represents something larger than a collection of prompts. It's evidence that agent skills are becoming infrastructure — the same way linters, formatters, and CI pipelines became standard.
Consider the parallels:
- Prettier standardizes formatting. Everyone on the team writes code that looks the same.
- Husky + lint-staged enforces checks before commits. Nobody skips the linter.
- Agent skills standardize how AI participates in your process. The agent doesn't just generate — it follows a workflow.
As AI coding tools become ubiquitous, the teams that differentiate won't be the ones using AI the most. They'll be the ones using AI the most disciplined way. Skills are how you encode that discipline.
FAQ
Q: Do these skills only work with Claude Code? A: They're designed for Claude Code's skill system, but the underlying patterns are markdown-based and framework-agnostic. You can adapt them for any AI coding assistant that supports custom instructions.
Q: Which skill should I start with? A: Start with grill-me. It's the fastest way to see the difference between "AI that writes code" and "AI that thinks through problems." Run it on any design decision you're currently wrestling with.
Q: Are agent skills the same as custom system prompts? A: No. A system prompt sets context and personality. A skill defines a repeatable multi-step workflow with specific inputs, outputs, and guardrails. It's closer to a CI pipeline than a prompt.
Q: Can I create my own skills? A: Yes — the repo includes a write-a-skill skill that teaches the pattern. Matt Pocock also runs a newsletter at aihero.dev where he shares new skills and updates.