Configure Your Project
Your Saved Setups
No saved configurations yet. Complete the wizard to save your setup.
Why This Wizard Saves You Time
Starting a new project involves many small decisions. Which folder structure? What dependencies? How to configure TypeScript? This wizard walks you through each choice with sensible defaults.
Each preset represents hours of community discussion and real-world usage. You get a working foundation without researching every option.
Preset Examples
| Stack | Use Case | Included |
|---|---|---|
| React + TypeScript + PostgreSQL | Full-stack web app | React, Express API, Prisma ORM, Jest tests |
| Vue + SQLite + Docker | Lightweight dashboard | Vue 3, Express, SQLite, Docker config |
| FastAPI + PostgreSQL | API-first service | FastAPI, SQLModel, Alembic migrations |
| Next.js + Supabase | Serverless full-stack | Next.js 14, Supabase client, Tailwind CSS |
Common Mistakes to Avoid
- Skipping the .gitignore file - always include it to avoid committing node_modules and secrets.
- Not pinning dependency versions - use exact versions in production, not "latest".
- Over-complicating folder structure - start simple and refactor as you grow.
- Ignoring environment variables - separate dev and prod configs early.
Before You Begin
Ask yourself: What problem does this project solve? Who will maintain it? These answers shape whether you need TypeScript, tests, or complex build tools. The wizard assumes you want a maintainable, shareable codebase.
Check your team's standards after generating. Some organizations require specific linting rules or CI/CD patterns not covered here.