메뉴
Strengthen the automated test suite standalone — codify untested behavior, fill coverage gaps on recent changes, add E2E for a critical flow, or stabilize flaky tests. Use when the user asks to add/improve/fix tests outside the full /ship pipeline.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Database engineering standards for PostgreSQL, MySQL, MongoDB, Supabase and Firebase/Firestore — schema/index design, security, and the per-engine gotchas an agent gets wrong. Loaded on top of backend-craft when a ticket touches the database. Use when designing schema, queries, migrations or data-access.
Next.js App Router full-stack standards — server/client boundaries, the four caching layers, server-action security, route handlers, rendering/streaming, metadata, middleware limits, and Next-specific testing. Loaded on top of react-craft (and alongside backend-craft for server code) when the ticket's stack is Next.js. Use when building any Next.js route, action, or API surface.
Headless QA tooling for driving real test tools from the CLI — Postman/Newman (functional + contract), OWASP ZAP + nuclei (security/DAST, the agent-drivable substitute for Burp), and k6/JMeter/autocannon (load). Use when running a comprehensive QA/security/load sweep against a running app.
Full delivery pipeline — takes a feature/project request, plans it into Jira-like markdown tickets, builds each ticket with specialized developer agents, then runs QA, security and code-audit agents, loops a debugger agent over findings until clean, and closes with a final report. Use when the user asks to build a feature or project end-to-end, or invokes /ship.
Express.js (Node) engineering standards — layering, async error handling (Express 4 vs 5), boundary validation, security middleware, graceful shutdown, and testing. Loaded on top of backend-craft when the ticket's stack is Express. Use when building Express APIs.
NestJS engineering standards — feature-module architecture, DI discipline, DTO validation, the guard/interceptor/pipe/filter split, config, TypeORM/Prisma, and testing. Loaded on top of backend-craft when the ticket's stack is NestJS. Use when building NestJS APIs.
| name | tests |
| description | Strengthen the automated test suite standalone — codify untested behavior, fill coverage gaps on recent changes, add E2E for a critical flow, or stabilize flaky tests. Use when the user asks to add/improve/fix tests outside the full /ship pipeline. |
| argument-hint | [coverage | e2e "<flow>" | flaky | <scope>] |
$ARGUMENTS:
coverage (or empty) — find and fill test gaps on the working-tree diff, or
the whole project if the diff is empty.e2e "<flow>" — build an end-to-end test for the named user journey.flaky — hunt tests that flicker (run the suite 3×, diff results) and
stabilize them at the root cause.test-engineer agent with the mission, the relevant paths, and
how to run the project/tests (from CLAUDE.md or workboard/steering/tech.md).Do not spawn reviewers or debuggers here — if the new tests expose real bugs,
list them and suggest /debug-findings.