メニュー
Use when the user explicitly wants to scaffold or plan a new application from scratch and needs high-level app setup, stack selection, or project structure guidance.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use the Codex Kit CLI to initialize, update, or inspect a Codex-ready project scaffold in the current workspace.
Use when a change may affect rollout, deployment, migrations, or operational stability and needs a higher-confidence validation pass.
Review patches, branches, or implementations for correctness, regressions, security, and missing tests. Use when the task is to inspect a diff or code change and identify concrete risks before merge.
Reproduce, isolate, and explain bugs before fixing them. Use when the task is about a bug, regression, failure, flaky behavior, unexpected output, or unclear runtime behavior that must be narrowed to a concrete cause.
Produce implementation plans that are decision-complete and execution-ready. Use when the task needs decomposition, sequencing, acceptance criteria, explicit assumptions, risk handling, or a concrete plan before coding or operational work starts.
Use when a bug is real but poorly scoped and you need a disciplined pass to reproduce it, bound it, and isolate the most likely root cause before fixing.
| name | app-builder |
| description | Use when the user explicitly wants to scaffold or plan a new application from scratch and needs high-level app setup, stack selection, or project structure guidance. |
Analyzes user's requests, determines tech stack, plans structure, and coordinates agents.
Read ONLY files relevant to the request! Check the content map, find what you need.
| File | Description | When to Read |
|---|---|---|
project-detection.md | Keyword matrix, project type detection | Starting new project |
tech-stack.md | 2026 default stack, alternatives | Choosing technologies |
agent-coordination.md | Agent pipeline, execution order | Coordinating multi-agent work |
scaffolding.md | Directory structure, core files | Creating project structure |
feature-building.md | Feature analysis, error handling | Adding features to existing project |
templates/SKILL.md | Project templates | Scaffolding new project |
Quick-start scaffolding for new projects. Read the matching template only!
| Template | Tech Stack | When to Use |
|---|---|---|
| nextjs-fullstack | Next.js + Prisma | Full-stack web app |
| nextjs-saas | Next.js + Stripe | SaaS product |
| nextjs-static | Next.js + Framer | Landing page |
| nuxt-app | Nuxt 3 + Pinia | Vue full-stack app |
| express-api | Express + JWT | REST API |
| python-fastapi | FastAPI | Python API |
| react-native-app | Expo + Zustand | Mobile app |
| flutter-app | Flutter + Riverpod | Cross-platform mobile |
| electron-desktop | Electron + React | Desktop app |
| chrome-extension | Chrome MV3 | Browser extension |
| cli-tool | Node.js + Commander | CLI app |
| monorepo-turborepo | Turborepo + pnpm | Monorepo |
| Agent | Role |
|---|---|
project-planner | Task breakdown, dependency graph |
frontend-specialist | UI components, pages |
backend-specialist | API, business logic |
database-architect | Schema, migrations |
devops-engineer | Deployment, preview |
User: "Make an Instagram clone with photo sharing and likes"
App Builder Process:
1. Project type: Social Media App
2. Tech stack: Next.js + Prisma + Cloudinary + Clerk
3. Create plan:
├─ Database schema (users, posts, likes, follows)
├─ API routes (12 endpoints)
├─ Pages (feed, profile, upload)
└─ Components (PostCard, Feed, LikeButton)
4. Coordinate agents
5. Report progress
6. Start preview