spoonai
GitHubSkillsClaude-CodeEngineering-Workflow

mattpocock/skills — A TypeScript Wizard's .claude/ Folder, Now 25K Stars

Matt Pocock open-sourced his .claude/skills/ directory verbatim and watched it explode to 25K stars in 72 hours — PRD → issue breakdown → TDD → guardrails as enforced workflow against vibe coding.

·4분 소요·GitHubGitHub
공유
mattpocock/skills GitHub OG card — 25,000 stars engineering workflow skills
Source: GitHub

25,000 Stars in 72 Hours

On April 29, Matt Pocock shipped his .claude/skills/ directory as an OSS repo. Three days later it sat at 25K stars, doing 1,100/day and 7,800/week. The packaging is unusual — there is no scaffolding code, no library, just markdown skills and bash hooks. What people are starring is a workflow.

The pitch fits in one line: "Not vibe coding — real engineering. PRD → issue breakdown → TDD → guardrails." Matt's tweet hit 4,200 retweets in 36 hours, and "fundamentals matter more than ever" became the rallying cry of the anti-vibe-coding camp.

Background — Who and Why

Matt is the founder of Total TypeScript, ex-Vercel DevRel, and the person 300K+ TypeScript learners know as the TypeScript Wizard. His shift to agent tooling started six months ago and he's been documenting it on AI Hero Substack.

The release was set up by an X-debate in mid-April: one camp arguing AI coding was already broken by vibe coding, another insisting the problem was that users dropped engineering fundamentals. Matt was a leading voice in the second camp, and "let me show you exactly how I work" turned into a public repo.

Core — 20+ Named Skills, Three Categories

Three groups, cleanly factored. Planning: to-prd (requirements → PRD), to-issues (PRD → GitHub Issues), grill-me (adversarial review of a spec), design-an-interface. Development: tdd (strict test-first with commit cadence), triage-issue, improve-codebase-architecture (multi-step refactor planner). Tooling: setup-pre-commit (Husky + lint-staged), git-guardrails-claude-code (block dangerous git commands at agent level).

Each Skill is markdown + bash hook, not just a prompt. The tdd Skill, for example, enforces the red-green-refactor cycle through slash commands and git hooks — the user doesn't have to remember the discipline; the workflow makes it.

git clone https://github.com/mattpocock/skills.git ~/.claude/skills/mattpocock
claude /skills
claude  # then invoke /tdd or /to-prd

Stack + Architecture

Markdown skills + Bash hooks + Claude Code SDK + Husky + lint-staged. It's a workflow repo, not a code repo — each Skill is 50-200 lines of markdown plus 10-30 lines of hooks, designed to be forked and tweaked.

The most interesting piece is git-guardrails-claude-code. It's not a .gitignore — it's pre-execution hooks that block force-push-to-main, blanket rm -rf, and committing secrets. Industrial-grade defense against the agent-runs-something-destructive failure mode.

Compete Set

Project Curator Stars Skill focus Note
mattpocock/skills Matt Pocock 25K PRD/TDD/git guardrails Workflow enforcement
anthropic/skills Anthropic 9K General examples Educational
wshobson/agents wshobson 14K Domain agents RAG/chatbot focus
Yeachan-Heo/oh-my-codex Yeachan Heo 6K Codex env setup Codex-locked

Matt's collection is differentiated on "workflow enforcement"; the others are mostly example libraries.

Why Now

Three currents collided. One: post-GPT-5.5 (April 23) and post-Opus 4.7 (April 16), the dev consensus settled on "function-level is solved, project-level still breaks" — and Matt's flow patches the exact cracks. Two: the April 24 Google + Forcepoint indirect prompt injection report turned agent autonomy into an active security worry, and git-guardrails-claude-code reads like the right tool at the right moment. Three: Anthropic shipped Skills as a first-class feature on April 17, opening up the OSS Skills market, and Matt's collection became its first viral hit.

The most-quoted Matt line: "Fundamentals matter more than ever in the AI era." It became the anti-vibe-coding catchphrase and his Substack subscribers tripled in April.

Getting Started + Pitfalls

Two pitfalls. One: if you already have skills in ~/.claude/skills/, drop Matt's collection in a subdirectory (mattpocock/) to avoid namespace collisions. Two: tdd assumes a working test runner (Vitest/Jest) is already set up — combine with setup-pre-commit on a fresh project.

Limits and Outlook

TypeScript/JavaScript bias is heavy, and some skills are still raw — the repo is four days old. The May PR cohort is bringing tdd-pytest, tdd-cargo ports, so multi-language coverage is moving fast. Long-term, Anthropic's rumored Skill Marketplace (early May) will probably feature mattpocock/skills as a curated headliner, which would make this repo the reference design for the OSS-Skill-curator category.

Tomorrow Morning

Developers: clone and apply tdd to one of your repos — first cycle takes 30 minutes. PM/founders: try to-prd + to-issues on next sprint planning to see how far an agent can substitute for planning craft in your context. Designers: this is coding-heavy, so use it as a window into how engineers actually work with AI rather than a tool for your stack.

References

관련 기사

무료 뉴스레터

AI 트렌드를 앞서가세요

매일 아침, 엄선된 AI 뉴스를 받아보세요. 스팸 없음. 언제든 구독 취소.

매일 30개+ 소스 분석 · 한국어/영어 이중 언어광고 없음 · 1-클릭 해지