Project Scaffolder
Generate production-ready starter repositories with best-practice conventions for any tech stack.
Core Workflow
- Determine stack: Ask user to specify or infer from context (Next.js, Vite, Nest, FastAPI, etc.)
- Select template: Use references/templates.md to choose the appropriate project structure
- Generate structure: Create complete folder tree with all necessary files
- Add baseline code: Include working "hello world" route/page as proof of concept
- Configure tooling: Add package.json/requirements.txt, tsconfig, linting, formatting configs
- Create scripts: Include dev, build, test, and deployment scripts
- Document setup: Generate comprehensive README with setup steps and next actions
Key Deliverables
Every scaffolded project must include:
- Folder tree: Well-organized src/, lib/, config/, tests/ structure
- Baseline code: Working hello world endpoint or page
- Package files: package.json, requirements.txt, Cargo.toml, etc.
- Configs: TypeScript, ESLint, Prettier, environment files (.env.example)
- Scripts: npm scripts or Makefile for common tasks
- README: Setup instructions, tech stack overview, next steps
- Git setup: .gitignore configured for the stack
Stack-Specific Patterns
See references/templates.md for detailed patterns per stack:
- Next.js App Router
- Vite + React
- NestJS
- FastAPI
- Express + TypeScript
- Vue + Vite
- SvelteKit
Best Practices
- Use absolute imports (@/ alias) where supported
- Include environment variable templates
- Add basic error handling and logging setup
- Configure path mappings in tsconfig
- Include Docker files for containerization (optional)
- Add GitHub Actions or CI workflow templates (optional)
Progressive Enhancement
Start with minimal viable structure, then add:
- Database setup (Prisma, TypeORM, SQLAlchemy)
- Auth scaffolding (NextAuth, Passport, JWT)
- API client setup (Axios, Fetch wrapper)
- State management (Zustand, Redux, Pinia)
- Testing setup (Jest, Vitest, Pytest)
Output Structure
Present the complete project tree first, then create all files in proper locations. Always provide a summary of what was created and next steps to run the project.
1---2name: project-scaffolder3description: Generates complete starter repositories for various tech stacks (Next.js, Vite, Nest, FastAPI, etc.) with best-practice conventions, folder structure, baseline code, configs, scripts, and setup documentation. Use when users request to "scaffold a project", "create a starter repo", "initialize a new project", or specify a tech stack to begin with.4---5
6# Project Scaffolder
7
8Generate production-ready starter repositories with best-practice conventions for any tech stack.
9
10## Core Workflow
11
121. **Determine stack**: Ask user to specify or infer from context (Next.js, Vite, Nest, FastAPI, etc.)
132. **Select template**: Use references/templates.md to choose the appropriate project structure
143. **Generate structure**: Create complete folder tree with all necessary files
154. **Add baseline code**: Include working "hello world" route/page as proof of concept
165. **Configure tooling**: Add package.json/requirements.txt, tsconfig, linting, formatting configs
176. **Create scripts**: Include dev, build, test, and deployment scripts
187. **Document setup**: Generate comprehensive README with setup steps and next actions
19
20## Key Deliverables
21
22Every scaffolded project must include:
23
24- **Folder tree**: Well-organized src/, lib/, config/, tests/ structure
25- **Baseline code**: Working hello world endpoint or page
26- **Package files**: package.json, requirements.txt, Cargo.toml, etc.
27- **Configs**: TypeScript, ESLint, Prettier, environment files (.env.example)
28- **Scripts**: npm scripts or Makefile for common tasks
29- **README**: Setup instructions, tech stack overview, next steps
30- **Git setup**: .gitignore configured for the stack
31
32## Stack-Specific Patterns
33
34See `references/templates.md` for detailed patterns per stack:
35
36- Next.js App Router
37- Vite + React
38- NestJS
39- FastAPI
40- Express + TypeScript
41- Vue + Vite
42- SvelteKit
43
44## Best Practices
45
46- Use absolute imports (@/ alias) where supported
47- Include environment variable templates
48- Add basic error handling and logging setup
49- Configure path mappings in tsconfig
50- Include Docker files for containerization (optional)
51- Add GitHub Actions or CI workflow templates (optional)
52
53## Progressive Enhancement
54
55Start with minimal viable structure, then add:
56
57- Database setup (Prisma, TypeORM, SQLAlchemy)
58- Auth scaffolding (NextAuth, Passport, JWT)
59- API client setup (Axios, Fetch wrapper)
60- State management (Zustand, Redux, Pinia)
61- Testing setup (Jest, Vitest, Pytest)
62
63## Output Structure
64
65Present the complete project tree first, then create all files in proper locations. Always provide a summary of what was created and next steps to run the project.
patricio0312rev