A partial stack is enough
Leave a question blank and it stays off the command. None does the same. App type is the one choice that sets the shape: Frontend Only drops the API, Backend Only drops the UI.
Pick a stack. Copy one command.
Choose the pieces of a repo: the frontend, the API, the database, and which coding agent should build it. Brix checks that those pieces can sit together, then writes the instructions into an empty folder. You paste one prompt, and the agent builds from those files.
Summary
Frontend
Next.jsVite + ReactSvelteKit
Backend
ExpressFastAPI
Coding agents
Claude CodeCodexCursor
npx usebrix@latest init --frontend vite-react --backend fastapi --agent claude-code
npx usebrix@latest init --frontend nextjs --backend express --agent cursor
What a run does
The line is the whole selection
Each answer becomes one flag. Repeat --agent once for Cursor, Claude Code, or Codex. Pass --yes to skip the confirm prompt, or --config to read a stack.json you already have.
Nothing is written if the pair is illegal
A Python-only API cannot take Node. Clerk cannot sit on Backend Only. The command exits before stack.json, the agent files, or any skill folder exists.
What it writes
A partial stack is valid. None never appears on the command.
stack.json
Choices, agents, and the registry version
AGENTS.md
Build instructions for the agent
CLAUDE.md
Pointer at AGENTS.md
PROMPT.md
The short prompt you paste into the agent
.agents/skills/
Skills for Cursor and Codex
.claude/skills/
Skills for Claude Code
What you can pick
Core
Frontend, UI, backend, package manager, runtime, database, ORM, and coding agents.
Services
Auth, payments, cache, storage, email, workflows, and testing.
Cloud
Monitoring, CI/CD, deploy, and containers.
Tools
Code index, reply style, implementation, memory, and a skill pack.
A Python-only API cannot take Node. Clerk cannot sit on Backend Only.