cypress-advanced
Use when advanced Cypress features including custom commands, plugins, and network stubbing.
Use when advanced Cypress features including custom commands, plugins, and network stubbing.
Use when working with TestNG annotations, assertions, test lifecycle, and configuration for Java testing.
TDD for process documentation - write test cases (pressure scenarios), watch baseline fail, write skill, iterate until bulletproof against rationalization.
Test quality guard - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies.
Flaky test fix pattern - replaces arbitrary timeouts with condition polling that waits for actual state changes.
RED-GREEN-REFACTOR implementation methodology - write failing test first, minimal implementation to pass, then refactor. Ensures tests verify behavior.
Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured.
Audit/regression checks for the evidence-first survey pipeline: citation health, per-section coverage, placeholder leakage, and template repetition. **Trigger**: auditor, audit, regression test, quality report, 审计, 回归测试. **Use when**: `output/DRAFT.md` exists and you want a deterministic PASS/FAIL report before LaTeX/PDF. **Skip if**: you are still changing retrieval/outline/evidence packs heavily (audit later). **Network**: none. **Guardrail**: do not change content; only analyze and report.
Add exercises to each tutorial module (inputs, expected outputs, verification steps) and update `outline/module_plan.yml`. **Trigger**: exercises, practice, verification checklist, 教程练习, 可验证作业. **Use when**: 已有模块计划(`outline/module_plan.yml`),需要为每个模块补齐至少 1 个可验证练习以形成 teaching loop。 **Skip if**: 还没有 module plan(先跑 `module-planner`)。 **Network**: none. **Guardrail**: 每个练习必须包含 expected output + verification steps;避免只给“思考题”无验收。
This skill should be used when writing tests, fixing bugs, adding features, or modifying the gateway layer. Use when you need guidance on testing architecture, working with fakes, implementing ABC gateway interfaces, or understanding the defense-in-depth testing strategy. Essential for maintaining test quality and understanding where different types of tests belong.
Execute and analyze Unity Test Framework tests from the command line. This skill automates test execution for Unity projects by detecting the Unity Editor, configuring test parameters (EditMode/PlayMode), running tests via CLI, parsing XML results, and generating detailed failure reports. Use this when running Unity tests, validating game logic, or debugging test failures.
Use to run pricing elasticity experiments with consistent assumptions and guardrails.
Generate frontend component tests (unit, snapshot, e2e). Auto-invoke when user says "test this component", "write component test", or "add component test".
Generate backend tests (unit, integration, mocks). Auto-invoke when user says "write test for", "add test", "test this", or "create test".
Write the test first, watch it fail, write minimal code to pass
Systematically inspect unit and E2E tests to verify they test the right behavior, provide meaningful coverage, and catch real regressions
Agent for validating Hex1b documentation against actual library behavior. Use when auditing documentation accuracy, testing interactive examples, or identifying discrepancies between documentation and implementation.
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Add new example use cases to the Examples feature
Run tests with local database setup and repository pattern
Use this skill for browser automation, E2E testing, visual regression testing, and web application testing with Playwright or similar tools.
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Your approach to handling testing coverage. Use this skill when working on files where testing coverage comes into play.