Testing
Unit tests, integration tests, test automation
implementing-figma-designs
by OneKeyHQ
Implements Figma designs 1:1 using OneKey component library (还原设计稿).
testing
by citypaul
Testing patterns for behavior-driven tests. Use when writing tests or test factories.
epic-testing
by epicweb-dev
Guide on testing with Vitest and Playwright for Epic Stack
playwright-ux-ui-capture
by raphaelmansuy
Capture EdgeQuake WebUI routes with Playwright and write artifacts immediately (screenshots + per-page request JSON + capture index). Use when adding/updating Playwright E2E capture specs or when asked to automate UI screenshot collection.
launch-marketing
by RefoundAI
Help users plan and execute product launches. Use when someone is planning a product launch, preparing PR outreach, coordinating a go-to-market campaign, launching on Product Hunt, or asking how to generate buzz for a new feature or product.
migration-workflow
by codewithmukesh
Safe migration workflows for EF Core database migrations, .NET version upgrades, and NuGet dependency updates. Includes rollback strategies and verification steps. Load when: "migration", "add migration", "ef migration", "update database", "upgrade nuget", "update packages", "dependency update", "version upgrade".
80-20-review
by codewithmukesh
Focus code review effort on the 20% of code that causes 80% of issues. Prioritizes data access, security, concurrency, and integration boundaries over formatting and style. Uses blast radius scoring to determine review depth. Includes checkpoint schedules, critical path identification, and a batch review checklist. Load this skill when reviewing code, PRs, or architecture, or when the user mentions "review", "code review", "PR review", "what should I review", "review priorities", "blast radius", or "critical path".
dashboard-build
by mckinsey
A skill that should be invoked whenever a user wants to build a Dashboard or simple app. This skill is Phase 2 of an e2e process that covers the actual build and testing. For Phase 1 (requirements, layout design, visualization selection), use the dashboard-design skill.
sdd-verify
by Gentleman-Programming
Validate that implementation matches specs, design, and tasks. Trigger: When the orchestrator launches you to verify a completed (or partially completed) change.
sdd-init
by Gentleman-Programming
Bootstrap the openspec/ directory structure for Spec-Driven Development in any project. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".
sdd-spec
by Gentleman-Programming
Write specifications with requirements and scenarios (delta specs for changes). Trigger: When the orchestrator launches you to write or update specs for a change.
spec-change
by event-catalog
Update the EventCatalog DSL specification across all locations — Langium grammar, specification markdown docs, playground examples, and tests. Use when making any change to DSL syntax, adding new DSL features, modifying grammar rules, or updating DSL documentation. Triggers on requests like "add X to the DSL", "update the grammar", "change DSL syntax for Y", or "spec change".
dashboard-design
by mckinsey
USE THIS SKILL FIRST when user wants to create and design a dashboard, ESPECIALLY Vizro dashboards. This skill enforces a 3-step workflow (requirements, layout, visualization) that must be followed before implementation. For implementation and testing, use the dashboard-build skill after completing Steps 1-3.
e2e
by NeverSight
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.
data-driven-testing
by NeverSight
"DEPRECATED: Use testing-best-practices instead. This skill has been retired."
specalign
by NeverSight
Align spec files with implementation. Detects drift between spec and code, surfaces discrepancies, user decides whether to update spec or code. Use when both a spec file and its implementation are in context.
e2e
by NeverSight
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.
data-driven-testing
by NeverSight
"DEPRECATED: Use testing-best-practices instead. This skill has been retired."
google-analytics
by henkisdabro
Comprehensive Google Analytics 4 guide covering property setup, events, custom events, recommended events, custom dimensions, user tracking, audiences, reporting, BigQuery integration, gtag.js implementation, GTM integration, Measurement Protocol, DebugView, privacy compliance, and data management. Use when working with GA4 implementation, tracking, analysis, or any GA4-related tasks.
quick
by FradSer
Streamlined code review for rapid assessment and targeted feedback. Use when reviewing small PRs, simple changes, or when you need a quick triage to determine if deeper review is required.
behavior-driven-development
by FradSer
Apply BDD principles including Gherkin scenarios and the Red-Green-Refactor cycle. Use when implementing features, fixing bugs, or refactoring to ensure test-driven development and shared understanding of requirements.
pr-build-status
by dotnet
"Retrieve and analyze Azure DevOps build failures for GitHub PRs. Use when CI fails. CRITICAL: Collect ALL errors from ALL platforms FIRST, write hypotheses to file, then fix systematically."
Project Guidelines Skill (Example)
by WorldFlowAI
tdd-workflow/ - Test-driven development methodology
dotnet-testing
by novotnyllc
Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing (DistributedApplicationTestingBuilder), snapshot testing (Verify, scrubbing), Playwright E2E browser automation, BenchmarkDotNet microbenchmarks, code coverage (Coverlet), mutation testing (Stryker.NET), UI testing (page objects, selectors), and AOT WASM test compilation. Spans 13 topic areas. Do not use for production API architecture or CI workflow authoring.