Anesis is a CLI tool for creating new projects from templates and extending existing ones with addons. This documentation covers installation, day-to-day usage, and how to build and publish your own templates and addons.
Log in, scaffold a project from a template, then apply an addon.
anesis login
anesis new my-app react-vite-ts
cd my-app
anesis addon install nest-drizzle
anesis use nest-drizzle install
# Or scaffold a template + a pinned set of addons in one shot
anesis new my-app --stack nest-drizzle-stackThree primitives — templates, addons, and stacks — cover the full project lifecycle.
Templates are project starters. Run anesis new my-app react-vite-ts and Anesis downloads the template, prompts for any inputs the template declares, renders every .tera file through those inputs plus the project name, and writes the output to disk.
Addons extend an existing project. Run anesis use nest-drizzle install and Anesis reads the addon manifest, detects your project variant, prompts for inputs, and applies declarative file operations — tracked so they can be undone with anesis undo.
Stacks tie the two together. Run anesis new my-app --stack <id>and Anesis scaffolds the stack's template, then applies its ordered list of addons with their inputs pre-filled — one command instead of a template followed by several anesis use calls.
All three are cached locally under ~/.anesis. Anesis only re-downloads when the backend reports a new commit SHA, and addon runs are recorded in anesis.lock.
Every page is focused on one job. Jump straight to what you need.
anesis.template.json, Tera rendering, and the project scaffolding contract.anesis.addon.json manifests with variant detection, inputs, and declarative file operation steps.anesis new --stack call.~/.anesis, cache/lock file fields, and validation rules.anesis mcp server for AI agents and CI.