メニュー
Architecture pattern reference for Next.js & React projects. Covers Flat, Feature-Based, FSD, and Monorepo patterns with core principles, file placement, and import boundaries.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Vercel 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.
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.
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.
| name | architectures |
| description | Architecture pattern reference for Next.js & React projects. Covers Flat, Feature-Based, FSD, and Monorepo patterns with core principles, file placement, and import boundaries. |
Reference guide for choosing and applying architecture patterns. Used by the /init agent when generating spec/ARCHITECTURE.md.
| Pattern | Team size | Core idea | When to use |
|---|---|---|---|
| Flat | Solo | Root-level sharing, no feature grouping | Prototypes, simple apps, < 10 features |
| Feature-Based | Small (2-5) | Self-contained feature modules with public API | Clear feature boundaries, medium complexity |
| FSD | Medium (5-15) | Strict unidirectional layer hierarchy | Complex domain logic, strict discipline needed |
| Monorepo | Large (15+) | apps/ + packages/ with Turborepo | Multiple apps, shared code, independent deploys |
Is this a solo prototype or simple app?
├─ Yes → Flat
└─ No → Does the team need strict layer rules?
├─ Yes → Is the team 15+?
│ ├─ Yes → Monorepo
│ └─ No → FSD
└─ No → Feature-Based
Flat → Feature-Based → FSD → Monorepo
Each pattern is a superset of the previous. Migration is incremental — you don't need to rewrite everything at once.
/init reads the detected pattern and applies the corresponding guide when writing spec/ARCHITECTURE.md