Use when the user says 'build me an app', 'create a project from this spec', 'scaffold a new repo', 'generate a starter', 'turn this idea into code', 'bootstrap a project', 'I have requirements and need a codebase', or provides a natural-language project specification and expects a complete, runnable repository. Stack-agnostic: Next.js, FastAPI, Rails, Go, Rust, Flutter, and more. Trigger phrases: "use when the user says 'build me an app', 'create a project from this spec', 'scaffold a new repo', 'generate a starter', 'turn this idea into code', 'bootstrap a project', 'i have requirements and need a codebase', or provides a natural-language project specification and expects a complete, runnable repository".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Use when the user says 'build me an app', 'create a project from this spec', 'scaffold a new repo', 'generate a starter', 'turn this idea into code', 'bootstrap a project', 'I have requirements and need a codebase', or provides a natural-language project specification and expects a complete, runnable repository. Stack-agnostic: Next.js, FastAPI, Rails, Go, Rust, Flutter, and more. Trigger phrases: "use when the user says 'build me an app', 'create a project from this spec', 'scaffold a new repo', 'generate a starter', 'turn this idea into code', 'bootstrap a project', 'i have requirements and need a codebase', or provides a natural-language project specification and expects a complete, runnable repository".
Spec to Repo
Turn a natural-language project specification into a complete, runnable starter repository. Not a template filler — a spec interpreter that generates real, working code for any stack.
When to Use
User provides a text description of an app and wants code
User has a PRD, requirements doc, or feature list and needs a codebase
User says "build me an app that...", "scaffold this", "bootstrap a project"
User wants a working starter repo, not just a file tree
Not this skill when the user wants a SaaS app with Stripe + Auth specifically — use product-team/saas-scaffolder instead.
Core Workflow
Phase 1 — Parse & Interpret
Read the spec. Extract these fields silently:
Field
Source
Required
App name
Explicit or infer from description
yes
Description
First sentence of spec
yes
Features
Bullet points or sentences describing behavior
yes
Tech stack
Explicit ("use FastAPI") or infer from context
yes
Auth
"login", "users", "accounts", "roles"
if mentioned
Database
"store", "save", "persist", "records", "schema"
if mentioned
API surface
"endpoint", "API", "REST", "GraphQL"
if mentioned
Deploy target
"Vercel", "Docker", "AWS", "Railway"
if mentioned
Stack inference rules (when user doesn't specify):
Signal
Inferred stack
"web app", "dashboard", "SaaS"
Next.js + TypeScript
"API", "backend", "microservice"
FastAPI (Python) or Express (Node)
"mobile app"
Flutter or React Native
"CLI tool"
Go or Python
"data pipeline"
Python
"high performance", "systems"
Rust or Go
After parsing, present a structured interpretation back to the user:
## Spec Interpretation
**App:** [name]
**Stack:** [framework + language]
**Features:**
1. [feature]
2. [feature]
**Database:** [yes/no — engine]
**Auth:** [yes/no — method]
**Deploy:** [target]
Does this match your intent? Any corrections before I generate?
Flag ambiguities. Ask at most 3 clarifying questions. If the user says "just build it", proceed with best-guess defaults.
Phase 2 — Architecture
Design the project before writing any files:
Select template — Match to a stack template from references/stack-templates.md
Define file tree — List every file that will be created
Map features to files — Each feature gets at minimum one file/component
Design database schema — If applicable, define tables/collections with fields and types
Identify dependencies — List every package with version constraints
Plan API routes — If applicable, list every endpoint with method, path, request/response shape
Present the file tree to the user before generating:
Every file referenced by an import exists in the tree
.env.example lists every env var used in code
.gitignore covers build artifacts and secrets
README has setup instructions that actually work
No hardcoded secrets, API keys, or passwords
At least one test file exists
Build/start command is documented and would work
Run scripts/validate_project.py against the generated directory to catch common issues.
Examples
Example 1: Task Management API
Input spec:
"Build me a task management API. Users can create, list, update, and delete tasks. Tasks have a title, description, status (todo/in-progress/done), and due date. Use FastAPI with SQLite. Add basic auth with API keys."
"I want a recipe sharing website. Users sign up, post recipes with ingredients and steps, browse other recipes, and save favorites. Use Next.js with Tailwind. Store data in PostgreSQL."
