Installation
stacks needs Node.js 20.19 or later. The CLI has no dependencies of its own: it is plain Node, with nothing to build. The generated projects have their own requirements (Yarn 4 through Corepack, Docker, Python 3.14 for py-worker), listed on each template’s page.
Run it once without installing:
npx @aurostack/stacks new nest-api ./apiOr keep the stack command around:
npm install -g @aurostack/stacksstack --versionUpdate with npm install -g @aurostack/stacks@latest. The package contains the
CLI and the templates, and nothing else.
Inside Claude Code:
/plugin marketplace add aurostack-org/stacks/plugin install stacks@aurostackThe plugin brings the CLI, the templates and seven skills:
/stacks:stack-newscaffolds a project. It asks which template and features you need, runs the CLI, and walks you through the setup the project still needs. It never hand-writes boilerplate the templates already contain./stacks:stack-setuptakes generated projects from installed to running locally: env values, local services, the first migration, the worker’s schema, the frontend’s API types, a check of each service. It never asks for credentials in chat, and writes what is left before production toSETUP.md./stacks:stack-addadds a feature to a project after it was generated (realtime, notifications, an admin console…). It runsstack add, which merges exactly what the feature changes and keeps your edits, then resolves any conflicts and lists the steps left (env values, migrations)./stacks:stack-upgradebrings a generated project up to the current templates withstack upgrade: what the templates changed since its release, merged in, your edits kept, with anything you exclude left alone./stacks:stack-from-designstarts from a finished claude.ai design and its design system. It works out what the screens need, from frontend to backend, agrees the plan and the folder layout with you, generates every project, applies the design system’s tokens to the UI kit theme and writes aBUILD-PLAN.md, including the gaps no template covers./stacks:stack-tasksturns thatBUILD-PLAN.mdinto a Linear project: PR-sized issues from backend to frontend, a milestone per phase, estimates, priorities and blockers. You review the whole list before anything is created, and re-running it updates the same issues./stacks:stack-syncfolds changes from a real project back into a template (for maintainers; see Refreshing templates).
You can also just ask for “a new API” or “a worker” and the skill picks it up. Building with Claude Code walks through how they fit together, from a design to a backlog.
To offer the plugin to everyone who opens a repository, commit this to the
repository’s .claude/settings.json:
{ "extraKnownMarketplaces": { "aurostack": { "source": { "source": "github", "repo": "aurostack-org/stacks" }, "autoUpdate": true } }, "enabledPlugins": { "stacks@aurostack": true }}Needed only to maintain the templates (stack extract refuses to run from
an npm or plugin install, because the next update would replace its work):
git clone https://github.com/aurostack-org/stacks.gitbash stacks/install.shinstall.sh is safe to re-run. It checks Node, links cli/stack.mjs as
stack into ~/.local/bin (or ~/bin; otherwise it prints an alias to add),
warns if another stack shadows it on your PATH, runs stack doctor, and
prints how to load the plugin from the checkout with
claude --plugin-dir <path> so skill edits apply without reinstalling.
Without installing anything, node cli/stack.mjs <command> works from the
checkout directly.
What each generated project needs
Section titled “What each generated project needs”| Template | Needs on your machine |
|---|---|
| nest-api | Node 24, Yarn 4 (corepack enable), Docker (for local Postgres and Redis) |
| nest-monorepo | the same as nest-api |
| react-app, react-monorepo | Node 24, Yarn 4 |
| next-site | Node 24, Yarn 4, Docker (for its local Postgres) |
| node-worker | Node 24, Yarn 4; the API’s Postgres and Redis |
| py-worker | Python 3.14; the API’s Postgres and Redis |
Generation runs yarn install (or creates a Python virtualenv) for you. If a
tool is missing, generation still finishes: the install step warns and you run
it yourself afterwards. See Your first project.