Your team's coding standards, in every AI session.
ACE loads your team's skills, MCP tools, and project context from one shared school, so every developer's Claude Code, Codex, or OpenCode session starts from your standards — not from whatever one person configured locally.
Works with Claude CodeCodexOpenCode
Built and dogfooded inside PRODIGY9, a working software consultancy — across multiple active client projects, every day.
Accelerated Coding Environment
Demo: a teacher curates a school of skills and MCP servers and shares it with
git push. Three teammates then run ace setup, launch their backend,
and write different code — all from the same shared standards.
- Curate a school
- Share it
- Teammate runs
ace setup - Launch the backend
- Code with shared skills
why teams use it
- Spread senior judgment across the team — not trapped in a few people or repos.
- Put product direction, technical standards, and project context into every coding session.
- Kill setup drift: skills, MCP tools, and backend context load from one source.
- Support different teams from one foundation, without forcing one workflow on everyone.
Built for the engineering leads who decide how their team builds — not just how one
laptop happened to get configured.
quick start
Latest version: vX.X.X
# macOS / Linux $ curl -fsSL https://ace-rs.dev/install.sh | bash # Windows (PowerShell) > powershell -c "irm https://ace-rs.dev/install.ps1 | iex" # Homebrew (macOS Apple Silicon) $ brew install ace-rs/tap/ace $ ace setup ace-rs/school # clone a school, register MCP, write config $ ace learn # study the project, narrow skills to what fits $ ace # launch your AI backend
Homebrew installs are managed by brew upgrade ace; ace upgrade is a no-op for brew installs. Intel macOS, Linux, and Windows: use the install scripts above or the release binaries.
build from source
Requires a Rust toolchain (rustup).
# Install latest from the main branch $ cargo install --git https://github.com/ace-rs/ace # Or clone and install from a working tree $ git clone https://github.com/ace-rs/ace $ cd ace $ cargo install --path .
what a school gives you
- A shared home for prompts, coding skills, conventions, MCP endpoints, and project context
- A practical way to spread your strongest technical practices beyond the people who already know them
- A feedback loop where teams improve shared skills once and reuse those improvements across projects
how it works
- 1. ACE resolves the active school, backend, and project settings for the current repository
- 2. It clones or updates the school cache and links shared folders into the backend workspace
- 3. It registers the MCP tools the team expects to have available
- 4. It composes session context from school guidance and project config
- 5. Then it hands off to Claude Code, Codex, or OpenCode with the environment ready to work