Claude Skills for Coding

A short coding-focused cut of our editorial ranking: methodology, clarification, and React performance—not the full top-ten list.

Coding intent, not another copy of the full ranking

If you arrived looking for Claude skills for coding, you do not need every card on the best Claude skills shortlist. You need a process for shipping code with Claude Code, a way to clarify fuzzy tickets before implementation, and—when the UI is already “done” but the page is slow—concrete React and Next.js performance rules.

This hub is a use-case cut of the same editorial ranking. Scores, publishers, and install lines match the home page as of Nov 21, 2026. Full narrative reviews live on skill pages; we do not invent a second scoring system here.

Coding with Agent Skills works best when you keep the context window quiet. Two methodology packs that both try to own the session usually fight. Prefer one session owner, then add a narrow task skill only when the job is narrow.

Superpowers — 95/100

Superpowers is a full Claude Code methodology skill: clarify the goal, write a readable plan, implement with tests, and review before you call the work done. It ranks #1 on our shortlist because the job is concrete and matches how people actually ship software in a terminal agent loop.

/plugin install superpowers@claude-plugins-official

Read the Superpowers review for who should skip it, how it differs from grill-me, and publisher notes. Treat it as one methodology—do not stack a second “do everything” pack beside it.

grill-me — 90/100

grill-me interviews you until fuzzy branches are resolved—before Claude writes a lot of code. It ranks #4 because it is small, composable, and high leverage on vague prompts like “rebuild onboarding” or “fix auth.”

npx skills add mattpocock/skills --skill grill-me

grill-me review. Useful before a Superpowers-style build when the ticket is still mushy. If you already know the answers, say so and move on; grilling is a tool, not a ritual.

vercel-react-best-practices — 87/100

When the regression is performance—not “make it pretty”—this Vercel Labs skill feeds Claude a ranked set of React/Next practices for slow pages and heavy bundles.

npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices

Full review. Pair with UI taste skills only when you also care about how the screen looks—see Claude skills for design. Verify suggestions in your own profiler; rules are not a substitute for measurement.

How to choose on a real week

  1. Fuzzy ticket → grill-me first.
  2. Clear build in Claude Code → Superpowers as the session owner.
  3. Perf regression on React/Next → vercel-react-best-practices for that thread.
  4. Always run the safe Claude skills checklist before install, and prefer pins when the marketplace or CLI allows it.

If you mainly live in the terminal loop, also read Claude Code skills for install paths and CLAUDE.md vs skills boundaries. For install mechanics, use How to install Claude skills.

What this hub refuses to do

It does not re-score skills differently from the home page. It does not list all ten ranking cards. It does not claim hands-on lab benchmarks we did not run. For documents, design, research, or authoring, use the matching hub from the home use-case row.

Back to the full ranking.

FAQ

What are the best Claude skills for coding?

Start with Superpowers for a full Claude Code workflow, grill-me when the request is fuzzy, and vercel-react-best-practices when the job is React/Next performance.

Should I install all three coding skills at once?

No. Use Superpowers or grill-me as the session owner, then add the React performance skill only when you are doing perf work.

Related