aidokit scaffolds a structured, adapter-agnostic, AI-assisted development workflow into any project — greenfield or brownfield — and lets you pick which AI coding CLI drives it. Zero LLM calls. No telemetry. Reproducible.
Node.js 20+ · Apache 2.0 · first-party adapters: Claude Code, Codex CLI, GitHub Copilot CLI.
aidokit itself never talks to a model. Every decision is deterministic; every CI run is hermetic.
The same inputs always produce the same tree. A byte-compare gate in CI catches drift before it lands.
One workflow, your choice of CLI. Swap Claude Code for Codex or Copilot without rewriting your project.
Stack packs detect Node, TypeScript, Python, React, and Go projects and emit tailored testing + lint conventions.
Read-before-write everywhere. No file is overwritten without a diff. Existing conventions are preserved.
Every breaking change ships with aidokit migrate. Upgrading the kit never means rewriting it.
No magic. Each step is a question with a sensible default and a documented exit code.
Full hook system, slash commands, MCP servers, two-stage review. The reference experience.
Read moreLean surface: CLAUDE.md, docs scaffold, Beads task graph. Same workflow, fewer primitives.
Read moreSame scaffold targeting Copilot's CLI. Lands the workflow without forcing a tool switch.
Read moremy-project/
├── CLAUDE.md
├── .claude/
│ ├── agents/
│ ├── commands/
│ ├── hooks/
│ └── skills/
├── docs/
│ ├── architecture/
│ ├── specs/
│ └── superpowers/
├── agent-artifacts/
└── .beads/
└── tasks.db
One aidokit init emits a CLAUDE.md tuned to your stack, a .claude/ engine directory with the full Standard conformance kit, a docs/ scaffold ready for ADRs and specs, and a Beads task database for stateful planning.
Nothing is hidden. Every file is plain text. You can read it, diff it, and delete what you don't need.