Skip to content

Ecosystem

Things that consume RAC artifacts or the RAC engine. Every entry is real and verified at the time of listing: it exists at the cited location and works against a released engine version. There are no planned or placeholder entries.

Name What it is Where
RAC dogfood corpus This repository's own product knowledge — requirements, decisions, roadmaps, prompts, designs — validated in CI by the engine it specifies decisions/
rac-artifacts Claude Code skill A project-level agent skill that teaches Claude Code to create, validate, and update RAC artifacts using the rac CLI .claude/skills/rac-artifacts/
MCP grounding example A runnable demo showing an agent connected to RAC Guide over MCP respecting a recorded decision that an unconnected agent violates examples/guide/
Amp setup A worked setup connecting Sourcegraph's Amp to RAC — it reads the generated AGENTS.md natively and queries the lore MCP server examples/amp/
Claude Code setup A worked setup connecting Claude Code to RAC — the generated CLAUDE.md, the lore MCP server, the rac-artifacts skill, and the optional pre-edit veto hook examples/claude-code/
Codex setup A worked setup connecting OpenAI Codex to RAC — it reads the generated AGENTS.md and queries the lore MCP server via config.toml examples/codex/
Cursor setup A worked setup connecting Cursor to RAC — it reads the generated AGENTS.md and queries the lore MCP server via .cursor/mcp.json examples/cursor/
GitHub Copilot setup A worked setup connecting Copilot in VS Code to RAC — the generated .github/copilot-instructions.md plus the lore MCP server in agent mode examples/copilot/

Adding an entry

An entry is one row in the table above. The criteria:

  • The thing exists — on disk in this repository or at a stated external location — and can be inspected; intentions and works-in-progress are not listed.
  • It consumes RAC artifacts or the RAC engine against a released version.
  • The row states what it is and where it lives, in one line.

Entries are added by a pull request changing the single table row. The project's contribution policy is pending; until it is published, external additions cannot yet be accepted.

Harness integration recipes

A harness integration (a worked examples/<client>/ setup connecting a coding agent to RAC) follows a template and a verification gate — see the integration recipes authoring guide. A recipe is listed here only after it is smoke-tested against a released engine version by running the grounding demo (examples/guide/) with the harness connected. Until then it ships as documentation carrying a verify against <client> <version> marker and stays off this table — the real-and-verified rule made a precondition of the row, not a courtesy.