Skip to main content

Frameworks

Pick the starting framework your project is built on. This is the empty code your build starts from — structurally distinct from Skills (agent knowledge).

Next.js

Production React with SSR, App Router, server actions, and Tailwind out of the box. The default for anything with multiple pages or that needs SEO.

Best for

Marketing sites, dashboards, SaaS, anything user-facing

Ships with

Next.js 15
React 19
Tailwind CSS
framer-motion
Radix UI primitives
lucide-react icons
clsx + tailwind-merge
zod
react
ssr
tailwind

Vite + React

A fast SPA with client-side routing. No SSR overhead. Pick this for apps that are mostly interactive (dashboards, tools, games) and don't need SEO.

Best for

Internal tools, dashboards, single-page apps, interactive demos

Ships with

React 19 (Vite)
Tailwind CSS
@tanstack/react-router
lucide-react
Radix UI (subset)
clsx + tailwind-merge
react
spa
vite

Vanilla (Minimal)

A single index.html with inline <script> and <style>. No framework, no router, no design system, no npm dependencies. The fastest path for one-page anything.

Best for

Landing pages, calculators, single-purpose tools, embeds, demos

Ships with

One index.html
Inline JS/CSS
No build, no install
no-build
simple
single-page

Vanilla (SPA)

A small vanilla SPA with primitives: hash router, reactive store, DOM helpers, design tokens. Still no framework — but more structure than the minimal scaffold.

Best for

Multi-page tools that do not need a framework, small dashboards

Ships with

Plain HTML5
Vanilla JS (ES modules)
Hash router + store
Design-token CSS
No build step
no-build
spa

Not sure which to pick?

The default is Next.js — it works for almost everything. Pick Vite + React if you want a snappier SPA without SSR overhead. Vanilla is for one-page demos or learning. You can always change later by starting a new project.

Frameworks — Codebase