Testing
Unit tests, integration tests, test automation
product-customer-discovery
by piperubio
Plan and run product-focused customer discovery interviews and synthesize actionable customer insights. Use when you need to define discovery goals/hypotheses, identify an ICP/segments, create a recruiting plan, write an interview guide, conduct interviews, analyze notes (themes, JTBD, pains/gains), and produce a discovery readout with opportunities, risks, and next experiments.
impeccable-harden
by SebastiaanWouters
"Skills-only equivalent of impeccable.style /harden. Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use for frontend and UI design tasks."
aico-subagent-driven
by yellinzero
Execute implementation plan by dispatching fresh subagent per task. Each task gets: Implementer → Spec Review → Quality Review. Two-stage review ensures both correctness and quality. Use this skill when: - Have implementation plan with multiple independent tasks - Want automated execution with quality gates after each task - Tasks are mostly independent (not tightly coupled) - User asks to "execute the plan", "run the tasks", "auto implement" Prerequisites: Must have plan from aico-frontend-plan, aico-backend-plan, or aico-*-task-breakdown skill. Process: For each task: Dispatch Implementer → Spec Review (passes?) → Quality Review (passes?) → Next task Review order: ALWAYS spec compliance first, THEN code quality.
Large Language Platform SDK Integration
by llpsdk
Use when integrating your agentic application with the Large Language Platform.
laravel-best-practices
by masterfermin02
Enforce Laravel Best Practices when generating code, reviewing code, and writing tests (SRP, skinny controllers, FormRequests, service/action classes, DRY, Eloquent/Collections, Blade query avoidance, eager loading, chunking).
pr-onboarding
by CAPHTECH
PR作成時に生成AIがPR本文にオンボーディングを記述するスキル。変更の契約を、レビューア・将来の自分・障害対応者に渡す。理解の再現性・反証可能性・運用可能性を同時に成立させる。 トリガー条件: - PRを作成する時（「PRを作成して」「プルリクを書いて」） - PR本文を充実させたい時（「PR説明を書いて」「PRオンボーディングして」） - 変更の影響を整理したい時（「この変更の影響範囲を整理して」） - レビューの準備をする時（「レビュー用に変更をまとめて」）
systematic-test-design
by CAPHTECH
ユニットテストとPBT（Property-Based Testing）を組み合わせた体系的テスト設計スキル。 「脳を使う場所」を原因推理から「プロパティとジェネレータの設計」へ移動させる。 4つの成果物（ユニットテスト、プロパティカタログ、ジェネレータ群、反例コーパス）を固定し、 意地悪レベル（L0-L8）を段階的に上げながら、反例を資産化して回帰テストに回収する。 トリガー条件: - 「体系的にテスト設計して」「テストを設計して」 - 「PBTでテスト設計して」「プロパティベーステストを書いて」 - 「ユニットテストを設計して」「テストケースを作成して」 - 「テストをもっと意地悪にして」「境界値を網羅して」 - 「ジェネレータを設計して」「反例を資産化して」 - 「テストの穴を探して」「プロパティカタログを作成して」 - ELDのGroundフェーズでL1-L3テスト設計時
test
by iamladi
Write or review tests following Kent C. Dodds testing principles - flat structure, composable setup, disposable fixtures. Use when the user asks to write tests, review tests, or convert legacy tests.
engineer-plan
by elliottrjacobs
Create structured implementation plans using parallel research agents. Use when the user says "plan this", "create a plan", "implementation plan", or after completing a tech spec. Breaks specifications into ordered, actionable tasks with effort estimates.
tdd
by iamladi
TDD enforcement during implementation. Reads tdd: setting from CLAUDE.md. Modes - strict (human approval for escape), soft (warnings), off (disabled). Auto-invoked by /implement.
golang-testcontainers
by baotoq
Write integration tests in Go using testcontainers-go with real databases, caches, and message queues in Docker containers. Covers PostgreSQL, MySQL, Redis, RabbitMQ, Kafka, and custom containers with idiomatic Go testing patterns.
code-dojo
by seonghyeonkimm
Interactive code learning through skeleton-based exercises. Use when a user wants to deeply learn a codebase, library, or programming concept by building it themselves. Triggers: "learn this codebase", "study this project", "teach me how this works", "I want to understand this library", "code dojo", "learn by building", "help me learn", "interactive coding exercise". Creates step-by-step exercises where the user fills in TODO implementations verified by tests or type checks.
code-review
by SebastiaanWouters
Comprehensive code review covering functionality, testing, QA, and AGENTS.md compliance. Triggers on "review code", "code review", "review this", "check my code". Validates correctness, test coverage, test quality, and guideline adherence.
知行合一
by d-wwei
"知行合一——实践-认识螺旋，做正确的事而非容易的事。"
Sloth-PSC-Eido
by wangguobao0215
B2B pre-sales consultant AI assistant covering six core capabilities: meeting minutes restructuring with sentiment analysis, layered research outline generation with hook questions, SCQA-based solution framework with rhetoric audit, competitive battle cards with attack/defense tactics, Socratic cognitive challenge engine (blind-spot radar, stress test, war-game sandbox), and post-meeting action packs (follow-up email, presence-building material, memory-recovery card). Use when user needs meeting minutes, research outlines, solution frameworks, competitive analysis, cognitive challenges, or post-meeting follow-ups.
golang-testing
by baotoq
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
context-engineering
by justgetAI
Human-readable context management for AI coding agents. Filesystem-based specs, tasks, and foundation docs. Ships features with full traceability via native Teams.
bullet-tracer
by SebastiaanWouters
Implement features using tracer bullet approach - build minimal end-to-end vertical slice first, then expand.
eld-debug
by CAPHTECH
ELD的デバッグ手法 - 法則（Law）視点でバグを分析・修正する。 バグを「法則からの逸脱」として捉え、証拠ループで系統的に解決する。 トリガー条件: - 「ELDでデバッグして」「法則視点でバグを調査して」 - 「証拠ベースでバグ修正して」「デバッグを体系的に進めて」 - バグ修正、障害調査、根本原因分析
qa-agent
by vishal2457
Creates a QA planning subtask tagged qa-plan using handoff-first context loading, lazy artifact reads, and compact JSON handoff output.
e2e-test-specialist
by k1lgor
Use this for writing end-to-end (E2E) tests that simulate real user interactions in browsers (Playwright, Cypress, Selenium).
product-prd
by elliottrjacobs
Write product requirements documents from feature ideas or brainstorm output. Use when the user says "write a PRD", "product requirements", "feature spec", or needs to formalize a product concept into a structured document.
eld-model-law-card
by CAPHTECH
Deprecated: /eld-spec-card law を使用してください。 このスキルは後方互換のためのエイリアスです。すべての呼び出しは /eld-spec-card law に転送されます。
aico-frontend-implement
by yellinzero
Execute frontend task implementation with TDD. Read task file, execute steps, verify each, update status. Use this skill when: - User asks to "implement task/plan", "start implementation", "execute plan", or "start coding" - Have task file (story- or standalone-) ready to execute - User asks to "use TDD", "write test first", or "test-driven" - User asks to "write tests", "add tests", "create tests" - Fixing UI bugs (write failing test first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - Task file in docs/reference/frontend/tasks/ (story- or standalone-) - Read design-system.md, constraints.md, design spec before coding Flow: Read Task → Read Constraints → Execute Steps → Verify → Test → Update Status