eng-tdd
Enforces disciplined RED-GREEN-REFACTOR cycle—write failing test first, watch it fail, write minimal code to pass, then refactor.
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-02 00:09
Testing & quality
13,026 results
eng-testing-anti-patterns
Use when writing or modifying tests, adding mocks, or considering test-only hooks—prevents common mistakes like testing mocks, polluting production with test…
tools-debugging-root-cause
Systematic debugging playbook for tracing failures backward through the call chain, adding instrumentation, and fixing bugs at their origin.
test-writer
Write test code. 100% coverage, SSR tests, edge cases. Use when writing tests, adding test coverage.
integration
Run and interpret coop's VM integration suite locally on Lima or remotely on Firecracker. Use when asked for integration testing or when…
mutation-check
Run cargo-mutants for changed coop logic and keep .cargo/mutants.toml synchronized. Use when logic-dense modules change, before refactors, or when asked to…
ts-qa
Prepare changelog and manual QA artifacts from implemented changes. Only explicitly triggered by user.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-value
Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes…
schema-drift-detector
Detects unrelated schema.rb changes in PRs by cross-referencing against included migrations. Use when reviewing PRs with database schema changes.
testing
Use when writing React hook tests, encountering test failures, flaky tests, cross-file contamination, or "Hook timed out" errors - Bun test patterns with…
benchmark
Measure and repair Plate/Slate performance, or review a performance design before running its applicable benchmark lanes. Use before writing, reviewing,…
issue-harvester
Maintain exhaustive Slate/Plate issue-closure ledgers from current issue, PR, test and local proof evidence.
verify
Review implementation ownership and verify Plate packages, editor states and registry artifacts through their actual proof owners. Use before writing a plan's…
slow-tests
Run the gated test classes that plain `pytest` skips (slow Docker/sandbox tests, live model-provider API tests, flaky tests, trio variants). Use when asked to…
umbraco-health-check
Create and localize custom Umbraco 17 Health Checks for backend C# and Razor frontend experiences, including multilingual Dictionary items and safe fallback…
add-test
Add an integration test for a specific tool in an existing collection. Creates a test file following the collection's established patterns. Use when adding…
web-e2e
Run, create, and debug Playwright e2e tests for the web app. ALWAYS invoke this skill using the SlashCommand tool (i.e., `/web-e2e`) BEFORE attempting to run…
code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding…
browser-testing-with-devtools
Chrome DevTools for live runtime data: DOM inspection, console logs, network traces, performance profiling. Use when building or debugging anything in a…
test-fix-loop
Self-continuing loop that fixes a deliberately failing test, reruns it, and exits cleanly when green. Smallest cooking-routines skill — pairs with the cooking…
Frontend Testing
Comprehensive frontend testing patterns including component tests (Jest/Vitest + RTL), visual regression (Playwright), accessibility (axe-core), and…
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration,…
vp-test-design
Decide whether a change needs a test, write it first when a cheap test path exists, and judge every new or existing test by the behavior it protects. Use when…