GAIA
Install

One command is
all you need.

GAIA gives you a production-grade React frontend and the Claude-native system to build everything else on it. The frontend is handled. You add your backend, your services, your domain logic, and Claude builds them inside GAIA's conventions.

$npx create-gaia@latest my-app
Prerequisite·Node.js ≥ 22.19.0. We recommend nvm or grab it from nodejs.org. macOS or Linux. On Windows, run inside WSL2.

One command writes a complete React 19 and TypeScript project to disk, with the Claude Code workflow already wired in. No config to write. No prompt library to assemble. Hooks and a commit gate enforce the conventions, no prompting required. The discipline is built in.

Work has a shape: every feature starts with /gaia-spec, a plan, and acceptance tests written before the code. Pre-commit hooks catch what slips. A merge audit has the last word.

npx create-gaia my-app
my-app/
.claude/
agents/        # code-review-audit
commands/       # /gaia-init, /setup-gaia-ci
hooks/          # guardrail hooks
rules/          # load-on-demand conventions
skills/         # /gaia-wiki, tdd, react-code, ...
.gaia/              # GAIA CLI, manifest
.github/workflows/ # standing CI
.husky/             # pre-commit
.specify/           # spec-driven workflow
.storybook/
app/                # React Router 7 app
test/               # Vitest, RTL, MSW
wiki/               # Obsidian project memory
CLAUDE.md           # project brain
package.json
eslint · vitest · playwright · vite · tsconfig configs
Project memory & rules
A Karpathy-style CLAUDE.md, plus rules and skills that load only when the work touches them. Conventions hold across sessions.
Quality gates
1,314 lint rules on every commit. A code-review-audit agent on every merge: security, performance, architecture.
Persistent knowledge
An Obsidian wiki, a hot cache, and handoff notes, so a new session never relearns the codebase.
A real test stack
Vitest, React Testing Library, Playwright, MSW, Storybook, Chromatic, wired and ready.
Standing CI
Workflows keep dependencies current, run a daily security audit, sync the wiki on commit, and prune stale branches.

That's it.

Now go build something.

Read the docs →See the Features →