メニュー
Generate or update MSW mock handlers and fixtures from feature spec API contracts. Use to set up mock infrastructure, generate feature-specific mocks, or check mock status.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | mock |
| description | Generate or update MSW mock handlers and fixtures from feature spec API contracts. Use to set up mock infrastructure, generate feature-specific mocks, or check mock status. |
| argument-hint | [feature-name] | --setup | --status |
| context | fork |
Parse $ARGUMENTS to determine mode:
--setup: Set up MSW mock infrastructure from scratch.
Spawn task-executor agent (haiku) with:
[HANDOFF]
TO: task-executor (haiku)
TASK: Set up MSW mock infrastructure
DONE-WHEN:
- mocks/server.ts, mocks/browser.ts, mocks/index.ts, mocks/handlers/index.ts created
- msw installed as devDependency
- Mock initialization added to app entry point
MUST-NOT:
- Overwrite existing mocks/ directory
READS:
- .claude/agents/lead-engineer-msw-mock.md (mock patterns)
[/HANDOFF]
--status: Report current mock status (read-only, no agent spawn).
Read and report:
mocks/ directory exist?mocks/handlers/mocks/fixtures/NEXT_PUBLIC_API_MOCKING in .env* filesmock: true in spec.md, check if a handler existsFeature mode (default — when $ARGUMENTS is a feature name):
Spawn task-executor agent (sonnet) with:
[HANDOFF]
TO: task-executor (sonnet)
TASK: Generate MSW mock handlers and fixtures for feature "[feature-name]"
DONE-WHEN:
- mocks/fixtures/[feature-name].ts created with typed mock data
- mocks/handlers/[feature-name].ts created with MSW handlers
- mocks/handlers/index.ts updated to include new handlers
- npx tsc --noEmit passes
MUST-NOT:
- Modify source code outside mocks/
READS:
- spec/feature/[feature-name]/spec.md (API Contracts section)
- .claude/agents/lead-engineer-msw-mock.md (mock patterns)
[/HANDOFF]
Pre-checks (before spawning):
mock is not true, ask user to enable it## API Contracts is empty/missing → STOP: "Add API contracts first (run /spec)"mocks/ doesn't exist → run --setup first, then proceedVercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
Implement a feature. Supports resuming interrupted work and team mode (--team flag). Reads spec/feature/[name]/spec.md and design.md, generates PLAN.md inside the feature directory, waits for user confirmation, then implements and verifies the feature.
AI-driven browser testing against feature specs. Default mode reads spec REQs and autonomously tests in a real browser via Playwright MCP. Also supports running existing Playwright test files, visual regression, and accessibility audits.
Check how well the current implementation matches the feature spec and evaluate code quality. Runs spec compliance review followed by code quality review. Optionally runs unit/integration test audit, logging audit, and security audit when strategy files exist. Does not modify code.
Run tests for a feature based on TEST_STRATEGY.md and feature-level TEST.md. Handles unit/integration test workflows. Use --setup to configure test strategy. Use /qa for browser, visual, and accessibility testing.