start-it is a guided CLI for scaffolding opinionated project baselines across backend, frontend, AI/ML, and DSA workflows.
Instead of asking users to pick from a flat template list, the CLI now walks through:
- app type
- implemented stack
- stack-specific options
- project metadata
- deterministic scaffold generation
Node.js + TypeScript + ExpressNestJSPython + FastAPI
React + ViteNext.js
Python + FastAPI ServingR Analytics PipelineC++ Inference Utility
C++Python
The prompt flow is stack-aware.
- Backend: databases, security preset, logging, monitoring, testing
- Frontend: routing, styling, optional
shadcn/ui, state, data fetching, testing - AI / ML: serving or runtime mode, packaging, tracking, validation, logging, testing
- DSA-specific: track, runner style, verification mode
npm install -g start-it-cliOr run it without installing:
npx start-it-clistart-it-cliThe CLI then guides the project setup interactively.
For the full command reference, flags, output-directory options, and non-interactive examples, see USAGE.md.
App type: Backend
Stack: Node.js + TypeScript + Express
Databases: PostgreSQL, Redis
Security preset: bcrypt + JWT
Logging: Pino
Monitoring: Prometheus-ready
Testing: Jest + Supertest
App type: Frontend
Stack: React + Vite
Routing: React Router
Styling: Tailwind CSS
UI add-on: shadcn/ui starter
State: Zustand
Data fetching: TanStack Query
Testing: Vitest + React Testing Library
App type: AI / ML
Stack: Python + FastAPI Serving
Serving mode: Realtime + batch endpoints
Packaging: MLflow-ready
Tracking: MLflow
Validation: Pydantic + Pandera
Testing: Pytest + HTTPX
App type: DSA-specific
Stack: Python
Track: Interview preparation
Runner style: Function-first
Verification: Pytest
Generation is deterministic and stack-specific.
- Backend projects generate service-ready API scaffolds
- Frontend projects start from a provider-style baseline and are then customized
- AI / ML projects generate serving, analytics, or inference workspaces
- DSA projects generate practice workspaces with sample problems and runner/test setup
Each generated project also includes:
.cursorrulesdocs/AGENTS.mddocs/instructions.md- stack-specific
README.md
npm install
npm run buildnpm run devnpm test- Contribution guide: CONTRIBUTING.md
- Local development: docs/DEVELOPMENT.md
- Architecture: docs/ARCHITECTURE.md
- CI / CD: docs/CI_CD.md
src/
├── cli.ts
├── generator.ts
├── workflow.ts
├── types.ts
├── templates/
├── frontend/
├── aiml/
├── dsa/
└── __tests__/
- Only implemented stacks are shown in the workflow
- Some older static templates still exist in the repository, but the main CLI path is now app-type driven
- Frontend generation prefers provider-style baselines when applicable, with deterministic post-processing afterward
MIT