Setup, update, and diagnose AI Dev OS in one command.
npx ai-dev-os init --rules typescript --plugin claude-code| Manual Setup | With CLI |
|---|---|
git submodule add x 3 repos |
npx ai-dev-os init (one command) |
| Copy template manually | Auto-copied |
| Merge hooks.json by hand | Auto-merged (with backup) |
| Check submodule health manually | npx ai-dev-os doctor |
| Update submodules manually | npx ai-dev-os update |
npx ai-dev-os initThe CLI will prompt you to select a rules preset and plugin:
AI Dev OS Setup
───────────────
? Select rules preset:
❯ TypeScript (Next.js)
Python (FastAPI)
? Select plugin:
❯ Claude Code
Kiro
Cursor
✔ Added submodule: .ai-dev-os/core
✔ Added submodule: .ai-dev-os/rules
✔ Added submodule: .ai-dev-os/plugin
✔ Copied template → CLAUDE.md
✔ Merged hooks → .claude/settings.json
✔ Created .ai-dev-os.yaml
Done! Next steps:
1. Edit CLAUDE.md to customize for your project
2. Run /ai-dev-os-init in Claude Code to generate L1/L2
3. See: https://github.com/yunbow/ai-dev-os#quick-start
npx ai-dev-os init --rules typescript --plugin claude-code -y| Command | Description |
|---|---|
ai-dev-os init |
Add submodules, copy templates, merge hooks |
ai-dev-os update |
Update submodules to latest or pinned version |
ai-dev-os doctor |
Check installation health (7 checks) |
Command details
# Update all submodules to latest
npx ai-dev-os update
# Check for updates without applying
npx ai-dev-os update --check
# Pin to specific version
npx ai-dev-os update --ref v1.3.0npx ai-dev-os doctorChecks:
- Git repository validity
.ai-dev-os.yamlconfiguration- Submodule initialization (core, rules, plugin)
- Template file existence
- Hooks integration status
Options
Usage: ai-dev-os init [options]
Options:
--rules <name> Rules preset (typescript | python)
--plugin <name> Plugin (claude-code | kiro | cursor)
--ref <tag> Pin to a specific version tag (default: "latest")
--no-hooks Skip hooks.json merge
--dry-run Show what would be done without executing
-y, --yes Skip interactive prompts, use defaults
Configuration File
The CLI creates .ai-dev-os.yaml in your project root:
version: "1.0"
core:
repo: https://github.com/yunbow/ai-dev-os
ref: latest
path: .ai-dev-os/core
rules:
name: typescript
repo: https://github.com/yunbow/ai-dev-os-rules-typescript
ref: latest
path: .ai-dev-os/rules
plugin:
name: claude-code
repo: https://github.com/yunbow/ai-dev-os-plugin-claude-code
ref: latest
path: .ai-dev-os/plugin
hooks:
merged: true
mergedAt: "2026-03-20T10:00:00Z"Available Presets
| ID | Name | Repository |
|---|---|---|
typescript |
TypeScript (Next.js) | ai-dev-os-rules-typescript |
python |
Python (FastAPI) | ai-dev-os-rules-python |
| ID | Name | Repository | Template | Hooks |
|---|---|---|---|---|
claude-code |
Claude Code | ai-dev-os-plugin-claude-code | CLAUDE.md | Yes |
kiro |
Kiro | ai-dev-os-plugin-kiro | AGENTS.md | -- |
cursor |
Cursor | ai-dev-os-plugin-cursor | .cursorrules | -- |
Design Decisions
The CLI is a delivery mechanism — it sets up git submodules, copies templates, and merges hooks. It does not contain rules or plugins itself.
| Decision | Reason |
|---|---|
| Bundle rules/plugin content inside the CLI package | Transparency and forkability would be lost |
| Replace git submodules with npm dependencies | Non-Node.js projects couldn't use AI Dev OS |
| Make the CLI mandatory | "Works without CLI" is a core design principle |
| Eliminate plugin repositories | The CLI is the "courier", not the "content" |
| Add GitHub App / OAuth integration | Overkill — git operations are sufficient |
The CLI automates what you could do manually with git submodule add and cp. If the CLI disappeared tomorrow, every AI Dev OS feature would still work via manual setup.
| Repository | Description |
|---|---|
| ai-dev-os | Framework specification and theory |
| rules-typescript | TypeScript / Next.js / Node.js guidelines |
| rules-python | Python / FastAPI guidelines |
| plugin-claude-code | Skills, Hooks, and Agents for Claude Code |
| plugin-kiro | Steering Rules and Hooks for Kiro |
| plugin-cursor | Cursor Rules (.mdc) |
| benchmark | Quantitative benchmark — guideline impact data |