cursor-principle-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-02 00:09
13,016 results
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and…
Use when evaluating test quality on modules containing business logic, calculation utilities, or state machines to determine whether the tests provide genuine…
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure tables have unique accessible names. Check native…
Use when the user wants to validate, lint, or audit agent skill files (SKILL.md). Use when they say "validate these skills," "check this repo's skills," "lint…
Test shell scripts with BATS (Bash Automated Testing System). Write, run, and debug tests for bash scripts.
Load testing with k6, web performance auditing with Lighthouse, profiling, and benchmark analysis.
Generate unit tests from source files using AI. Use when adding test coverage.
End-to-end testing -- Playwright E2E suites, Cypress E2E, API testing with supertest, load testing with k6, and test reporting.
UI testing with Playwright and Puppeteer -- browser automation, visual regression, screenshots, and accessibility audits.
Unit testing across languages -- Jest, Vitest, pytest, Go test, Rust test, coverage, and watch mode.
Screenshot comparison testing with Playwright, Percy, and Chromatic for catching unintended UI changes.
Use when writing or reviewing tests in a Ruby/Rails application. Guides agents to write well-structured tests using the Arrange/Act/Assert pattern, semantic…
Use when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran…
Enforce reproducible testing, automated verification, and evidence-driven sign-off before merging any change.
Enforces disciplined RED-GREEN-REFACTOR cycle—write failing test first, watch it fail, write minimal code to pass, then refactor.
Use when writing or modifying tests, adding mocks, or considering test-only hooks—prevents common mistakes like testing mocks, polluting production with test…
Systematic debugging playbook for tracing failures backward through the call chain, adding instrumentation, and fixing bugs at their origin.
Write test code. 100% coverage, SSR tests, edge cases. Use when writing tests, adding test coverage.
Run and interpret coop's VM integration suite locally on Lima or remotely on Firecracker. Use when asked for integration testing or when…
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…
Prepare changelog and manual QA artifacts from implemented changes. Only explicitly triggered by user.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes…
Detects unrelated schema.rb changes in PRs by cross-referencing against included migrations. Use when reviewing PRs with database schema changes.