Testing

jherr-dev-workflow

by adrianbrowning

Iterative development workflow based on "Make it work, Make it right, Make it fast" philosophy. Use when building software features, components, or systems from scratch. Guides Claude through three distinct phases - getting a working solution first, then refactoring for quality, and finally optimizing performance only when needed. Prevents premature optimization and over-engineering. Integrates seamlessly with TDD (Test-Driven Development) by mapping test phases to development phases.

pricing-strategy

by alexwelcing

Develop optimal pricing models and positioning for products/services

_workflow-data-pipeline

by TriNgo0108

Lifecycle for building data pipelines, analytics engineering, and data quality checks. Follow the phases sequentially.

aeo-spec-validator

by ivzc07

Validate that tasks are sufficiently defined before execution. Returns score 0-100.

Tech Tutor (Ren Nakamura Persona)

by PrakharMNNIT

Intuition-first tech mentor who makes complex concepts click through visuals, analogies, and the 6-layer explanation framework. Use this skill when the user asks to "explain", "tutor", "teach", "mock interview", or needs intuition regarding DSA, System Design, or AI/ML.

qa

by AgustinAlbonico

"Alias corto para ejecutar pruebas E2E y QA manual. Usar cuando quieras probar la ultima funcionalidad implementada con /qa."

testing-e2e

by agdev

Expert guidance for writing resilient end-to-end tests that span multiple processes and components. Use this skill when reviewing, writing, or refactoring system-wide e2e tests. Covers user-facing scenarios, helper functions, data factories, ARIA-based selectors, and auto-retriable assertions. NOT for unit/integration tests - use testing-unit-integration skill instead. See references/playwright-resilience.md for detailed selector patterns.

IBM VPC File Pool CSI Driver — Build Skill

by neil1taylor

Do NOT skip leader election for the controller — two controllers allocating simultaneously will corrupt pool state.

build-trading-strategies

by robonet-tech

"AI-powered generation of complete trading strategy code. Uses create_strategy and create_prediction_market_strategy to transform requirements into production-ready Python code. Most expensive AI tool ($1.00-$4.50 per generation). Generates complete Jesse framework strategies with entry/exit logic, position sizing, and risk management. Use after exploring data and optionally generating ideas. ALWAYS test with test-trading-strategies before deploying."

ghwf2-spec

by ShotaIuchi

仕様書ドキュメントを作成

plan

by biruk741

Plan a complex coding task with adversarial review. Explores the codebase, asks clarifying questions, drafts a plan, then iterates with Codex for adversarial review against 10 quality criteria. Falls back to Claude-only if Codex unavailable. Does NOT create files — use /parallelize after.

dispatching-parallel-agents

by Cygnusfear

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

api-security-testing

by ncdevshiv

"API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices."

assertion-helper

by Protagonistss

分析函数逻辑并生成合适的断言。

peat-node

by defenseunicorns

Per-repo skill for the Peat sidecar node — Rust binary that exposes peat-protocol over Connect/gRPC/gRPC-Web for co-located applications, plus Helm/Zarf packaging.

unit-test

by kyzooghost

Guidelines for writing and reviewing unit tests. Covers AAA pattern, test naming, determinism, mocking strategies, and reviewer responsibilities. Use when creating or updating .test. files, reviewing test PRs, or refactoring tests to improve clarity and coverage.

doit

by 1JayPeng

Full spec-driven, TDD-based development workflow. Auto-classifies requests into simple/feature/bug, routes to correct flow, and enforces spec alignment through every step. Use when user states any requirement, feature request, or idea that involves writing or modifying code. Triggers on: "我想做", "帮我加", "我需要", "add feature", "implement", "I want to", "build", or any request that implies new functionality.

ab-test-setup

by samChang72

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.

Systems Engineering Skill

by HowardKao-1130

scrum-delivery-lead

by garbray

Scrum Master & Engineering-Oriented Delivery Lead with hands-on frontend/backend development experience. Interprets Technical Design Documents, reviews UX/UI designs, and understands product requirements to ensure delivery clarity. Breaks features into well-scoped Scrum stories (max 3 story points, Fibonacci estimation). Stories are sliced for incremental value, minimal risk, fast feedback. For every ticket provides: clear description, explicit acceptance criteria, expected behavior, constraints, and test case expectations (happy path + edge cases). Ensures stories are implementation-ready, testable, aligned with technical/product goals. Enables team to execute efficiently while maintaining high quality and predictable velocity. Use when creating sprint stories, planning sprints, estimating work, or breaking down features into tickets.

Test Verification Skill

by contohmarie

For testing repository identity verification

auto-decide

by mbaranovski

'Use when facing multiple implementation options, design alternatives, or architectural choices during planning, brainstorming, or coding. Triggers: "which approach", "option A vs B", "we could either...", or any choice between implementation paths that would otherwise stall progress.'

prd-generator

by oyi77

Generate detailed Product Requirement Documents (PRDs) from feature descriptions. Create structured specifications ready for implementation.

Testing

by tachfineamnay

Jest unit tests, Playwright E2E tests, fixtures, and CI integration.