Skill Finder
Search Claude skills
30 results for "write tests first"
-
1
Get write-product-specwrite-product-spec
For teams that want a behavior-first PRODUCT.md spec written before a feature is built. Skip it if the change is a small fix or you need a technical design doc.
-
2
Get superpowerssuperpowers
For developers who want Claude to follow a fixed design, plan, test-first and review routine on every task. Skip it if you prefer quick, unstructured edits.
-
3
Get tddtdd
For developers who want Claude to build features test first, one failing test at a time. Skip it if you want a whole test suite written in one go.
-
4
Get karpathy-guidelineskarpathy-guidelines
For developers who want Claude to ask before guessing, keep changes small and prove work with tests. Skip it for quick throwaway scripts where the caution slows you down.
-
5 Get systematic-debugging
systematic-debugging
For developers whose AI keeps guessing at fixes and who want the root cause found first. Skip it if you just need a typo or one-line slip corrected.
-
6 Get writing-plans
writing-plans
For developers who give Claude a spec and want a test-first build plan before any code is written. Skip it for small fixes you could make in one step.
-
7 Get brainstorming
brainstorming
For anyone who wants Claude to pin down what they really want before it builds. Skip it if your requests are already precise and you want work to start at once.
-
8
Get angular-developerangular-developer
For Angular developers who want Claude to write version-aware, current Angular code and check it builds. Skip it if you work in React, Vue or another framework.
-
9
Get golang-testinggolang-testing
For Go developers writing, reviewing or debugging tests, from table-driven cases to fuzzing and leak checks. Skip it if your code is not in Go or you only need testify API details.
-
10
Get vitestvitest
For JavaScript and TypeScript developers writing or fixing Vitest tests and config. Skip it if your project runs Jest, Mocha or another runner and you are not moving to Vitest.
-
11 Get spec-driven-implementation
spec-driven-implementation
For teams building large features who want PRODUCT.md and TECH.md specs checked in before and during coding. Skip it for small bug fixes or if you do not track work in Linear.
-
12
Get vercel-react-best-practicesvercel-react-best-practices
For React and Next.js developers who want slow pages and heavy bundles fixed by a ranked rulebook. Skip it if you do not write React or Next.js code.
-
13
Get commit-commandscommit-commands
For developers on GitHub who want commits, pushes and pull requests done with one command. Skip it if you write every commit message yourself.
-
14
Get playwrightplaywright
For developers who want Claude to drive a real browser to click, fill forms and test pages. Skip it if you cannot run Node.js on your machine.
-
15 Get skill-creator
skill-creator
For anyone writing their own Claude skills who wants test runs and a review loop. Skip it if you only install skills that other people made.
-
16 Get pr-review-toolkit
pr-review-toolkit
For developers who want separate, focused checks on comments, tests, error handling and types before a PR. Skip it if one general review is enough.
-
17 Get pyright-lsp
pyright-lsp
For Python projects where Claude should see type errors and move through code like an editor does. Skip it if you do not write Python.
-
18 Get ralph-loop
ralph-loop
For developers with a well-defined task and a checkable finish line who want Claude to keep iterating alone. Skip it for vague goals or taste calls.
-
19
Get supabasesupabase
For developers building on Supabase who want auth, RLS and migrations handled with care. Skip it if your backend runs on plain Postgres or another platform.
-
20 Get mcp-builder
mcp-builder
For developers turning an API or service into tools Claude can call through MCP. Skip it if you only want to use a server someone else already built.
-
21 Get skill-creator
skill-creator
For anyone writing Claude skills who wants a guided draft, test and improve loop. Skip it if you only need a one-off prompt.
-
22
Get slackslack
For Slack teams who want Claude to search, sum up and post messages, and for Slack app builders. Skip it if your team is not on Slack.
-
23 Get grill-with-docs
grill-with-docs
For people who want a plan or design questioned hard, with decision records and a glossary written along the way. Skip it if your plan is already settled.
-
24
Get solana-devsolana-dev
For developers building Solana programs, clients or wallet UIs who want current tooling defaults. Skip it if you are not working on Solana.
-
25
Get expo-moduleexpo-module
For Expo developers who need native Swift or Kotlin code exposed to their React Native app. Skip it if ready-made Expo packages cover your needs or you're moving to the 2.0 macros.
-
26
Get git-commitgit-commit
For developers who want Claude to stage and commit changes with Conventional Commits messages. Skip it if you only want a message drafted, or need pushes and rebases.
-
27
Get Scientific Agent SkillsScientific Agent Skills
For researchers who want Claude to run analyses with scientific Python tools in biology, chemistry or statistics. Skip it if your work never touches lab data or research code.
-
28
Get mastramastra
For TypeScript developers building agents and workflows with Mastra who want Claude to check current APIs first. Skip it if you do not use Mastra.
-
29
Get mcp-apps-buildermcp-apps-builder
For TypeScript developers building MCP servers or interactive MCP Apps with the mcp-use framework. Skip it if you write MCP servers in Python or with a different SDK.
-
30
Get seo-auditseo-audit
For site owners and marketers asking why pages don't rank or why traffic fell. Skip it if you only need structured data added or pages built at scale.