Best Claude skills for coding
Coding skills change how your agent works, not only what it writes: brainstorm before building, write a plan, test first, review its own diff, and finish branches cleanly. Packs like Superpowers, Matt Pocock's skills, Addy Osmani's agent skills and Garry Tan's gstack are the most starred skills on GitHub.
484 coding skills · ranked live · November 2026
The top 10. Ranked by the Alyn Score.
- 1#1
Matt Pocock
Diagnosing Bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
321k33MScore 97 - 2#2
Ask Matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
321k33MScore 95 - 3#3
Code Review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code…
321k33MScore 95 - 4#4
Jesse Vincent
Superpowers
Jesse Vincent
Writing Skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
316k3.9MScore 94 - 5#5
Jesse Vincent
Superpowers
Brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a…
316k3.9MScore 92 - 6#6
Jesse Vincent
Superpowers
Diagnosing Superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why…
316k3.9MScore 92 - 7#7
JuliusBrussee
Caveman Learn
Act on a Caveman learn report - review the ranked token sinks, apply cost-lowering fixes with per-edit consent, and report what those fixes returned. Use when asked to lower an agent's…
119k4.8MScore 90 - 8#8
affaan-m
Agent Architecture Audit
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering…
301k1.7MScore 89 - 9#9
Agent Sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes…
301k1.7MScore 89 - 10#10
Android Clean Architecture
Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring…
301k1.7MScore 89
What makes a great coding skill.
A workflow (plan, implement, verify) rather than a list of tips.
Explicit stop conditions so the agent asks instead of guessing.
Skills that compose: planning, testing and review that hand off to each other.
All 484 coding skills.
Matt Pocockteach
Teach the user a new skill or concept, within this workspace.
Matt Pococktriage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
Matt Pocockwayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination…
Matt Pocockwriting-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Matt Pocockcodebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more…
Matt Pocockto-tickets
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…
Matt Pocockwizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar…
Matt Pocockwriting-shape
Writing, exploit: shape raw material into an article, paragraph by paragraph.
Matt Pocockchief-of-staff
Pursue a long-running goal in a single session by co-ordinating subagents.
Matt Pocockgit-guardrails-claude-code
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git…
Matt Pocockpr
Use when writing a PR body.
Matt Pocockretro
Conduct a retrospective on a coding session.
Matt Pocockwriting-beats
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
Matt Pocockdomain-modeling
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.
Matt Pocockscaffold-exercises
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new…
Jesse Vincent
Superpowers
Jesse Vincentsubagent-driven-development
Use when executing implementation plans with independent tasks in the current session
Jesse Vincent
Superpowers
Jesse Vincentsystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Matt Pococktdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Matt Pocockto-spec
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.
Matt Pocockwriting-fragments
Writing, explore: mine raw fragments, no structure yet.
Matt Pocockgrilling
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.
Matt Pocockimplement-spec
Implement the result of /to-spec and /to-tickets in code.
Matt Pocockloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Matt Pocockmigrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Matt Pocockprototype
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.
Matt Pococksetup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or…
Matt Pocockto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Matt Pocockclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Jesse Vincent
Superpowers
Jesse Vincentdispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Jesse Vincent
Superpowers
Jesse Vincentexecuting-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Jesse Vincent
Superpowers
Jesse Vincentfinishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Jesse Vincent
Superpowers
Jesse Vincentreceiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not…
Jesse Vincent
Superpowers
Jesse Vincenttest-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Jesse Vincent
Superpowers
Jesse Vincentusing-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree…
Jesse Vincent
Superpowers
Jesse Vincentwriting-plans
Use when you have a spec or requirements for a multi-step task, before touching code
affaan-mapi-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing…
Coding skills, explained.
Also searched as: claude code skills, best claude code skills, software engineering skills, superpowers.
What are the best Claude skills for coding?
Right now the top-ranked coding skills on Alyn are Diagnosing Bugs (Matt Pocock), Ask Matt (Matt Pocock), Code Review (Matt Pocock). Rankings combine GitHub stars, installs, freshness and depth, and update live.
What are the best Claude Code skills?
By stars and installs: Superpowers (obra), Matt Pocock's skills, Addy Osmani's agent-skills, gstack (Garry Tan) and Caveman. Alyn ranks them live.
How many skills should I install?
Start with one workflow pack and two or three task skills. Each skill only costs about 100 tokens until it is used, but overlapping skills can confuse which one runs.
How do I install a coding skill?
Run npx skills add owner/repo in your project, or copy the folder with SKILL.md into ~/.claude/skills. Every skill on this page has a ready-to-copy command.
More in Build
Coding skills for your agent