Testing
Unit tests, integration tests, test automation
5d-build
by tapania
"Execute implementation tasks with quality and awareness. Use when: (1) After TASKS phase in 5D-SDD workflow, (2) Tasks are defined and sequenced, (3) User is ready to write code, (4) User asks to 'implement,' 'build,' or 'code' a task. This phase produces working code while maintaining connection to spec intent."
writing-plugins
by ApeWorX
Create a new Plugin for Ape Framework to integrate a specific tool or service into one of Ape's vertical(s). Use when users need specific best practices and guidance on developing a new plugin for Ape. Do not use if such a plugin already exists that is designed to work with Ape, and instead suggest that.
test-automation
by spjoshis
Master test automation with Selenium, Cypress, Playwright, framework design, and maintainable automated tests.
prd-writing
by meriley
Creates lean Product Requirements Documents from scratch or refines rough product ideas into actionable PRDs. Follows Agile methodology with user stories, acceptance criteria, and scope boundaries. Use when starting new features, documenting product ideas, or formalizing requirements.
coroutines-kotlin
by spjoshis
Master Kotlin coroutines with suspend functions, flows, channels, and structured concurrency for building async applications.
csharp-tdd-develop
by JeongHeonK
TDD 기반 C#/.NET 개발. 테스트 먼저 작성 후 구현. Red-Green-Refactor 순서 강제. 서브에이전트에 위임.
conducting-customer-research
by amogha-dalvi
Use when starting any marketing initiative, entering a new market, refreshing ICP, or when downstream marketing decisions lack customer evidence. Use when messaging isn't resonating, churn patterns are unclear, or positioning feels like guesswork. Foundational skill that feeds all other marketing skills.
improving-testing
by lucianghinda
Produces practical, risk-based testing guidance and minimal test plans for features or changes. Use when user asks what to test, how to pick test cases (boundaries, permissions, state machines), how to improve weak tests, or to review existing tests. Covers equivalence partitions, boundary values, decision tables, and state transitions.
context-compression
by eyadsibai
Use when compressing agent context, implementing conversation summarization, reducing token usage in long sessions, or asking about "context compression", "conversation history", "token optimization", "context limits", "summarization strategies"
docfactory-arch-expo
by burakdirin
Creates 04-tech-architecture.md (stack decisions, data layer, integrations, folder tree, deployment, security) for a new app idea using the Expo/React Native stack. Use after docfactory-uiux to define the technical implementation details. Essential for ensuring a scalable, maintainable foundation for a solo developer.
managing-marketing-ops
by amogha-dalvi
Use when the CRM is unreliable or inconsistently used, when lead routing is manual and slow, when marketing tools are disconnected or underutilized, when there are no documented SOPs for repeatable marketing processes, when marketing and sales lack shared definitions and handoff SLAs, or when data quality is degrading. Use when operational infrastructure is blocking execution of other marketing skills.
complete-spec
by jschulte
Interactive conversation to resolve [NEEDS CLARIFICATION] markers using /speckit.clarify command. Claude asks questions about missing features, UX/UI details, behavior, and priorities. Updates specs in .specify/memory/ with answers to create complete, unambiguous documentation. This is Step 5 of 6 in the reverse engineering process.
reverse-engineer
by jschulte
Deep codebase analysis to generate 11 comprehensive documentation files. Adapts based on path choice - Greenfield extracts business logic only (tech-agnostic), Brownfield extracts business logic + technical implementation (tech-prescriptive). This is Step 2 of 6 in the reverse engineering process.
wfc-lfg
by sam-fakhreddine
Executes the full WFC pipeline autonomously: plan → deepen → implement → review → resolve → test → push PR. Zero human interaction during execution. Terminal output is a PR on success; halts with a structured report on failure. Requirements: - Git repository with configured remote and clean working directory. - Authenticated gh CLI. - Target branch (default: develop) must exist on remote. Trigger: /wfc-lfg; "full wfc auto"; "ship it end to end" (requires active code context); regex pattern "^lfg (implement build add create refactor fix) .{20,}$" Not for: single-stage requests (route to that skill), deployment/infra tasks, auth/encryption/compliance/PII features (need human review), requests with approval gates, vague descriptions (e.g., "fix some issues"), repositories with uncommitted changes, requests contradicting guardrails (e.g., "push to main").
kubernetes-orchestration
by spjoshis
Master Kubernetes with pods, deployments, services, ingress, ConfigMaps, secrets, and production cluster management.
writing-sdks
by ApeWorX
Create a Python SDK using Ape Framework to simplify using a given blockchain-based protocol. Use when users need specific best practices and guidance on developing a new integration with the given protocol. Do not use if such a Python SDK already exists that is designed to work with Ape.
helm-production-patterns
by meriley
Implement production deployment strategies including secrets management, blue-green deployments, canary releases, and upgrade procedures. Use when deploying charts to production, implementing secrets management, setting up blue-green or canary deployments, configuring chart testing strategies, or planning upgrade and rollback procedures.
use-case-development
by spjoshis
Master use case development with actors, scenarios, preconditions, postconditions, and detailed specifications for comprehensive requirements.
product-backlog-management
by spjoshis
Master product backlog management with prioritization frameworks, refinement techniques, estimation, and continuous backlog optimization for maximum value delivery.
find-core-ideas
by ricardogomes
First-principles thinking; identify what everything else builds on. Use when a learner feels like they're memorizing rather than understanding, wants to distinguish foundational from derived concepts, or needs to reconstruct knowledge from basics. This skill guides through dependency testing (elimination, reconstruction, abstraction descent) while enforcing human-only reasoning about what's core vs. derived. Triggers on phrases like "I'm memorizing not understanding", "what's really foundational", "I can use it but don't understand why", "distinguish core from derived", or when a learner wants deeper understanding of first principles.
obra-test-driven-development
by faulkdev
Use when implementing new behavior or fixing bugs via tests-first (TDD) in VS Code Copilot Agent mode.
WordPress Test Analyzer Skill
by CrazySwami
```
feature-spec-writing
by meriley
Creates focused feature specifications with user stories, acceptance criteria, and edge cases. Lighter than PRD, focuses on single feature implementation. Use when specifying individual features after PRD approval or for standalone feature work.
setup-go
by meriley
Sets up Go development environment with proper tooling, linting, testing, and dependencies. Runs go mod tidy, configures golangci-lint, sets up testing framework, and verifies build. Use when starting work on Go projects, after cloning Go repositories, setting up CI/CD for Go, or troubleshooting Go environment issues.