Skip to content

Developers

Ritual lives inside your coding agent. Install the CLI, run ritual init, then call /ritual build during planning to surface the questions and tradeoffs the agent would otherwise invent.

CLI Install @ritualai/cli, run ritual init — sign-in, workspace bind, and skill scaffolding in one command.
Slash commands Four /ritual subcommands: build, resume, lineage, context-pulse.
MCP server Connect any MCP-capable client to mcp.ritualapp.cloud over Streamable HTTP.
API keys Personal access tokens — create, scope, rotate, revoke.

The shortest path

npm install -g @ritualai/cli
cd ~/your-project
ritual init

ritual init does four things in one pass:

  1. Signs you in (browser OAuth)
  2. Mints a long-lived Personal Access Token
  3. Binds this repo to a Ritual workspace
  4. Scaffolds the /ritual skill into every coding agent it detects

Then restart your agent and run:

/ritual build <feature description>

That’s the whole loop — context → scope → discovery → recommendations → build brief → implementation.

When to reach for which

  • Planning a feature — /ritual build "<description>" inside your agent. The full loop runs end-to-end.
  • Picking up a paused build — /ritual resume reloads the exploration’s context.
  • Scoring a vague ask before building — /ritual context-pulse "<description>" returns a Reasoning Readiness / Context Debt score with per-dimension breakdown. See the Context Pulse reference.
  • Finding what shaped a file — /ritual lineage <file-path> returns prior decisions, recommendations, and explorations that touched it.
  • Building your own MCP client — connect directly to mcp.ritualapp.cloud/mcp over Streamable HTTP. See the MCP server reference.

Supported coding agents

Claude Code, Cursor, Windsurf, Kiro, Gemini CLI, VS Code (Copilot), Codex. ritual init auto-detects what’s installed and scaffolds the same /ritual skill into each one’s config.