菜单
Create a practical test strategy that coding agents can extend consistently. Use when a repo needs unit/integration/e2e conventions, fixtures, test command wrappers, examples, or a bug-fix rule that starts with a failing reproduction test.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Diagnose failed or unreliable agent workflows by classifying bad assumptions, missing observations, tool misuse, wrapper failures, hidden repair loops, incomplete validation, handoff gaps, and repeated failure patterns. Use after a failed harness run, flaky agent output, or confusing validation loop.
Review agent-generated changes against project rules. Use when asked for a review, before opening a PR, after large Codex edits, or when checking diffs for correctness, security, architecture, tests, docs drift, dependencies, migrations, and release risk.
Generate or maintain a minimal high-signal AGENTS.md for coding agents. Use whenever a repo needs agent instructions, an existing AGENTS.md is too long or vague, or project docs/scripts need a concise routing map for Codex.
Define and mechanically enforce architecture boundaries for a repo. Use when a project needs allowed dependency rules, forbidden imports, layer documentation, dependency maps, circular dependency checks, or protection against agent-created architectural drift.
Scaffold a new TypeScript web, mobile, API, or full-stack project with Better-T-Stack, then harden it with the Pax Fullstack Harness. Use whenever the user wants a new TypeScript app scaffold, mentions Better-T-Stack, asks for a modern type-safe stack, or wants Codex to start a repo that is agent-ready from day one.
Use guided Chrome DevTools MCP setup and workflows for browser runtime debugging. Use when a web app needs console, network, DOM, accessibility, Lighthouse, performance, responsive, or live-browser investigation beyond normal tests.
| name | testing-strategy-builder |
| description | Create a practical test strategy that coding agents can extend consistently. Use when a repo needs unit/integration/e2e conventions, fixtures, test command wrappers, examples, or a bug-fix rule that starts with a failing reproduction test. |
Make tests easy for agents to add correctly by defining taxonomy, commands, fixtures, naming, and examples.
Use tdd-playwright-workflow for strict red-green-refactor execution, failing bug reproductions, or Playwright browser workflows.
Classify tests.
Normalize commands.
scripts/test.scripts/test-unit, scripts/test-integration, and scripts/test-e2e only when the repo can support them.scripts/test target unit/integration paths explicitly so it does not discover Playwright specs; keep Playwright behind scripts/test-e2e.scripts/validate.Document conventions.
Add examples.
assets/templates/playwright-e2e.spec.ts.tmpl only when Playwright is already present or the task explicitly accepts adding browser e2e tooling.aria-label or an equivalent component prop.Align CI.
tdd-playwright-workflow when a change must prove behavior through unit and Playwright tests before implementation.termination-gatekeeper to require e2e evidence when changed files cross UI, API, runtime, or data boundaries.When fixing a bug, add a failing reproduction test first unless impossible. If impossible, document why in the final response or PR validation notes.
./scripts/test.