One command restores your context, 186 skills and 10 MCP servers across six AI CLIs, on a brand-new Mac.
Most devs who use AI assistants daily end up with skills scattered across
~/.claude/, ~/.codex/, MCP servers hardcoded with no version control,
and the Spec→Plan→Execute→Verify loop living only in their head. AI-OS puts all of it
in one git repo, and keeps the products it builds out of it once they outgrow it.
Karpathy's framework as recurring workflows, hard rule-sets, and verifier gates applied after every task. One active Spec at a time; nothing ships without a runtime check.
14 required superpowers + 172 curated & vendored skills, symlinked into Claude Code, Codex, Gemini, Antigravity, Hermes & MiniMax. Plus 16 more hand-picked from a 272-skill ECC snapshot.
10 MCP servers as declarative YAML, generated at install. zsh, Warp, Brewfile & git config versioned in the same repo.
Everything above apps/ is the operating system. What it builds lives under apps/ until it needs its own release cadence, then it splits out.
diagram-design skill, skinned from context/06_brand.md.
Plansmith started as one more directory under this repo's apps/: a scraper,
a corpus, a formatter, a daily pipeline, a Vue explorer. It ran the same Spec →
Verifier → Environment loop as everything else here, one 30-minute block at a time,
until it was large enough to need its own release cadence.
apps/data/.Spec quality first, verifier passes second, runtime evidence third. No "it builds, ship it."
One active spec: objective, acceptance criteria, non-goals, risks.
Blocks of ≤30 min, dispatched in parallel when independent.
Verify after each block. Sub-agents self-report; you check the handles.
Quality checklist, self-critique, source-check. Evidence before "done".
Pick your OS. Copy the block. Most of the 30–60 min first install is just downloading packages.
# 1. bootstrap (clones + runs the Mac installer) npx @edd_remonts/create-ai-os cd ai-os # 2. verify (20 health-check sections) bash setup/verify.sh
# PowerShell as Admin: bootstrap (clones + runs the Windows installer) npx @edd_remonts/create-ai-os cd ai-os powershell -ExecutionPolicy Bypass -File .\setup\verify-windows.ps1
# Debian / Ubuntu: same bootstrap, cross-platform installer npx @edd_remonts/create-ai-os cd ai-os bash setup/verify.sh
git, curl and an internet connectionsetup/install-ecc.sh: the full 272-skill ECC snapshot as a Claude Code pluginsetup/install-claude-tools.sh: 12 more claude.tools / gstack skillsDRY_RUN=1: simulate without touching your machineThe installer prints this list and asks for confirmation before touching anything. Nothing is installed silently.
git, gh, node, python, uv, go, rust, docker, kubernetes-cli, terraform, ripgrep, fzf, bat, eza, lazygit, ollama, helm… Homebrew
claude-code, codex, gemini-cli, MCP servers, typescript, vite, eslint, prettier, biome, turbo, nx… via pnpm
ruff, black, mypy, pytest, ipython, pandas, numpy, httpx, typer, bandit, pip-audit, poetry, mcp… isolated uv venv
Symlinked into every CLI (Claude, Codex, Gemini, Hermes, Antigravity, MiniMax) plus the 14 required superpowers. ai-config/skills
/action /full /gen-html /saas-review /fix-ui-ux and 4 more, in every CLI that supports slash commands. ai-config/commands
Memory stack (FalkorDB + Ollama + Graphiti + code indexers via Docker), MCP config, Oh My Zsh + Powerlevel10k, dotfile symlinks. background layers
Stop reconfiguring six CLIs by hand. Put the method, the skills and the environment in one repo, and bring it back in one command.