Testing
Unit tests, integration tests, test automation
django-tdd
by affaan-m
Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
check-frontend
by mindfold-ai
"Check if the code you just wrote follows the frontend development guidelines."
break-loop
by mindfold-ai
"Break the Loop - Deep Bug Analysis"
harden
by pbakaus
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.
adversarial-ux-test
by NousResearch
Roleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.
verification-loop
by affaan-m
"A comprehensive verification system for Claude Code sessions."
python-testing
by affaan-m
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
terraform-skill
by antonbabenko
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions
interview-mock-partner
by aipoch
Simulates behavioral interview questions for medical professionals.
Work on Ticket
by zapier
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKET_ID]" or similar phrases.
tdd
by mattpocock
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
writing-plans
by obra
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills
by obra
Use when creating new skills, editing existing skills, or verifying skills work before deployment
systematic-debugging
by obra
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
llm-test
by elie222
Guidelines for writing tests for LLM-related functionality
dispatching-parallel-agents
by obra
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
subagent-driven-development
by obra
Use when executing implementation plans with independent tasks in the current session
migrate-to-shoehorn
by mattpocock
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.
testing
by elie222
Guidelines for testing the application with Vitest
backtest-expert
by tradermonty
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
pinecone
by NousResearch
Managed vector database for production AI applications. Fully managed, auto-scaling, with hybrid search (dense + sparse), metadata filtering, and namespaces. Low latency (<100ms p95). Use for production RAG, recommendation systems, or semantic search at scale. Best for serverless, managed infrastructure.
sparc-methodology
by ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
migrate-to-shoehorn
by mattpocock
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.
tdd
by mattpocock
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.