菜单
Use throughout the build and before claiming any phase or the project "done", to run the four mandatory quality gates and verify them with evidence. Covers the test pyramid, Playwright + Chrome DevTools browser verification, WCAG AA, and the commit/finish gate wiring.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when building or structuring a Python backend on FastAPI + SQLAlchemy 2.0 (async) + Alembic + Pydantic v2. Provides the opinionated project layout, the standard kit (auth, async jobs, caching, storage, observability), and best practices.
Use near the end of a project to generate CI and make the app deploy-ready. Produces a polyglot GitHub Actions workflow (lint, typecheck, test, build) and multi-stage Dockerfiles. The finish line is CI-green and container-ready, not an actual deploy.
Use when starting a frontend or working on its look and feel, to establish and enforce a DESIGN.md-driven custom design system as the single source of truth for tokens, components, and icons. Make any generated UI (including 21st.dev Magic output) conform to DESIGN.md.
Use when setting up local development services or running the project locally. Establishes the "stateful services in Docker, app runs native" pattern with Postgres, Redis, MinIO, and Mailpit.
Use after the plan is signed off, to drive the autonomous, plan-gated build to completion. Orchestrates per-task implementation, review, and verification in customer-experience-first order, stopping only on genuine blockers.
Use when building or structuring a React/Next.js + TypeScript + Tailwind frontend, choosing libraries, or wiring design tokens. Provides the opinionated blessed-library stack and the React-vs-Next decision, all on-token to DESIGN.md and accessible to WCAG AA.
基于 SOC 职业分类
| name | testing-and-quality |
| description | Use throughout the build and before claiming any phase or the project "done", to run the four mandatory quality gates and verify them with evidence. Covers the test pyramid, Playwright + Chrome DevTools browser verification, WCAG AA, and the commit/finish gate wiring. |
Announce at start: "I'm using claude-engineer:testing-and-quality to enforce the four quality gates."
No "done" without all four gates passing, verified by fresh evidence. (Pairs with
superpowers:verification-before-completion - assertions follow evidence, never precede it.)
vitest run --coverage; BE pytest --cov=app --cov-fail-under=80.playwright test (specs include a console-error/pageerror fixture and assert no 4xx/5xx on key routes). Drive flows and confirm every button/screen works via the Playwright + Chrome DevTools MCPs.playwright test a11y/ using @axe-core/playwright with tags wcag2a,wcag2aa,wcag21aa,wcag22aa; assert zero violations. Manual keyboard/focus spot-checks too.tsc --noEmit && eslint . && prettier --check . && ruff check . && ruff format --check . && mypy app.scripts/quality-gate.mjs from templates/quality-gate.mjs. It runs all four gates and writes
.claude-engineer/quality-gate-status.json ({ allPass, results }).git commit unless that file shows allPass: true.
So: run node scripts/quality-gate.mjs → fix failures → commit. Intentional bypass: git commit --no-verify.claude-engineer:ci-cd-pipeline).templates/recommended-mcps.md.Full detail (test pyramid, coverage targets, Playwright setup, the console-error fixture, axe usage, exact commands):
read references/testing-and-gates.md on demand.
--no-verify only with explicit reason).