GAIA
Install

One command is
all you need.

GAIA gives you a production-grade React frontend and the harness 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.22.0. We recommend nvm or grab it from nodejs.org. macOS or Linux. On Windows, run inside WSL2.

One command writes a monorepo to disk, with a React 19 and TypeScript frontend and the GAIA harness 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 Audit Team
commands/       # /gaia-init, /setup-gaia
hooks/          # guardrail hooks
rules/          # load-on-demand conventions
skills/         # /gaia-wiki, tdd, update-deps, ...
.gaia/              # GAIA CLI, manifest
.githooks/          # pre-commit, commit-msg
.github/workflows/  # test + visual CI
frontend/           # React Router 8 app
.claude/        # frontend rules and skills
.storybook/
app/
test/           # Vitest, MSW
wiki/               # Obsidian project memory
CLAUDE.md           # project brain
pnpm-workspace.yaml # workspace root
package.json
Project memory & rules
A short CLAUDE.md, plus rules and skills that load only when the work touches them. Conventions hold across sessions.
Quality gates
Over 1,200 lint rules on every commit. The Code Audit Team on every merge in Claude Code: security, performance, architecture, with a lighter review for a change proven small.
Persistent knowledge
An Obsidian wiki, plus specs, plans, and run state on disk, so a new session never relearns the codebase.
A real test stack
Vitest, Playwright, MSW, Storybook, Chromatic, wired and ready. Components are tested as stories in real Chromium, with accessibility checked on every story.

That's it.

Now go build something.

Read the docs →See the Features →