Starter Templates
Pre-configured full-stack starters available in BhaiCode Cloud Studio.
Each starter includes TypeScript, modern styling, and zero-config deployment support.
| Stack | Engine | Best for |
|---|---|---|
| React + Vite + Tailwind | Vite 6, React 19, Tailwind CSS v4 | Dashboards, internal tools, SPAs |
| Next.js | Next.js 15 (App Router), React 19, Tailwind CSS v4 | SEO sites, full-stack portals |
| Astro | Astro 5, content collections, islands | Docs, marketing sites, blogs |
| Remix / React Router v7 | React Router v7, TypeScript | Data-dense, form-heavy apps, ecommerce |
| SvelteKit | Svelte 5 runes, Vite, Tailwind CSS v4 | Lightweight utilities, tiny bundles |
Choosing a stack
Recommended for client-heavy SPAs.
- Routing: TanStack Router or React Router
- Styling: Tailwind CSS v4 with modern color functions and responsive utilities
- Pick it when the app is mostly interactive UI and SEO is not the priority.
Server-first React.
- Features: Server Components, Server Actions, API routes
- Styling: Tailwind CSS v4 and Lucide icons
- Pick it when you need SEO, server routes, or dynamic content.
Zero-JS by default.
- Features: Content collections, selective React hydration
- Pick it when pages are mostly content with occasional interactivity.
Data flows through loaders and actions.
- Features: Nested routes, resilient server rendering
- Pick it when the app is form-heavy or data-dense.
Minimal runtime.
- Features: Svelte 5 runes (
$state,$derived,$effect) - Pick it when bundle size is critical.
How a template boots
Virtual filesystem
Cloud Studio loads the project tree into an in-memory filesystem.
In-browser bundling
The WebAssembly compiler bundles your code locally in the browser — no remote containers to wait for.
AI context mapping
Bhai reads framework conventions, routing, and design tokens so generated code matches the template’s architecture.
Was this page helpful?