ワンクリックで
implement-test-phase
Implement a numbered testing strategy phase from docs/testing_strategy_phases/phase_$ARGUMENTS_*.md step by step
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Implement a numbered testing strategy phase from docs/testing_strategy_phases/phase_$ARGUMENTS_*.md step by step
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement a numbered phase from docs/phases/phase-$ARGUMENTS.md step by step
Review changed code for correctness, security, and project conventions. Invoke this skill automatically whenever a complete unit of work is done — a full implementation phase, a complete feature (repository + service + route + component all connected), or just before creating a PR. Do NOT invoke after editing a single file or mid-way through a feature. If the user says "done", "finished", "phase complete", "ready to commit", or similar, trigger this review immediately.
Run prisma migrate dev, regenerate client to the correct output path, and verify import paths
Scaffold a Prisma-backed repository for a given Prisma model
Scaffold a service class for a given domain following project conventions
Final pre-commit check: run type-check (npx tsc --noEmit), lint (npm run lint), and tests (npm test)
| name | implement-test-phase |
| description | Implement a numbered testing strategy phase from docs/testing_strategy_phases/phase_$ARGUMENTS_*.md step by step |
| disable-model-invocation | true |
| argument-hint | [phase-number] |
Read @docs/testing_strategy_phases/00_overview.md. You are about to implement Test Phase $ARGUMENTS.
docs/testing_strategy_phases/phase_$ARGUMENTS_*.md and read it ENTIRELY — all subsections — before writing any code.npm install only (never yarn, pnpm, or bun)..claude/rules/testing.md before writing any test files.tests/unit/ — pure logic, no DB, no networktests/integration/ — real DB with transaction rollback in afterEach; never mock the DBtests/components/ — React component tests with jsdomtests/e2e/ — Playwright end-to-end testsunit (node), integration (node), components (jsdom)tests/e2e/auth.setup.ts — never re-login inside a testdependencies: ['setup'] and storageState: 'playwright/.auth/user.json'waitForSelector, waitForResponse, or expect(locator).toBeVisible()@/app/generated/prisma/client — NEVER @prisma/clientPrismaClient outside src/lib/prisma.ts*.spec.ts or *.spec.tsx in tests/tests/fixtures/*.fixture.ts, tests/fixtures/mocks/*.mock.tsFollow the phase's numbered subsections in sequence — they are ordered by dependency.
npx tsc --noEmit
npm run lint
npm test
Manual checklist:
tests/ subdirectoryafterEach — no committed test dataauth.setup.ts storage state, not mid-test login@/app/generated/prisma/clientThen invoke the code-review skill — a completed phase is a full feature boundary.