Prototype Builder
Scaffold runnable prototype projects with make start support.
Workflow
- •Understand the request - Identify project type and tech stack
- •Select or validate stack - Use default or check user's choice
- •Create project - Copy template or generate dynamically
- •Verify runnable - Ensure
make startworks
Project Types & Templates
| Type | Template | Command |
|---|---|---|
| Full-stack Web | assets/nextjs-fastapi/ | Frontend + Backend |
| API Service | assets/fastapi-simple/ | Backend only |
| CLI Tool | assets/python-cli/ | Command-line app |
For other combinations, generate dynamically following the same patterns.
Tech Stack Selection
When user specifies a stack:
- •Check compatibility (see references/tech-stack-guide.md)
- •If reasonable → proceed
- •If problematic → explain concerns and suggest alternatives
When user doesn't specify:
Select based on project type:
- •Web app → Next.js + FastAPI
- •API service → FastAPI
- •CLI tool → Python
Project Creation
Default location
code
~/projects/<project-name>/
Using templates
bash
cp -r assets/<template>/* <target-path>/
Then customize:
- •Update
README.mdwith project name/description - •Adjust configuration as needed
- •Verify
make startruns successfully
Dynamic generation
For non-template stacks, create:
- •
Makefilewithstart,installtargets - •Entry point file(s)
- •Dependency file (requirements.txt, package.json)
- •
.gitignore - •
README.md
Success Criteria
| Project Type | "make start" Result |
|---|---|
| Web app | Browser shows page at localhost |
| API service | /health returns {"status": "ok"} |
| CLI tool | Runs and shows output |
Boundaries
Do NOT:
- •Write business logic code
- •Configure production deployment
- •Set up database migrations
- •Add authentication systems
- •Create complex architectures
Focus: Minimal runnable skeleton only.