Developers

Ritual works inside your coding agent. Install the CLI, run /ritual commands during planning, and pull approved exploration context through the MCP server.

CLIInstall @ritual-ai/cli, scaffold skills into your project, and pick light or cloud mode.

Slash commandsReference for /ritual explore, run, brief, gate, build, and the rest.

MCP serverConnect any MCP-capable editor to Ritual over Streamable HTTP.

API keys & scopesCreate, scope, and rotate keys from the Developer tab.

The shortest path

npm install -g @ritual-ai/cli
ritual init        # scaffold skills into .claude/, .cursor/, etc.
ritual login       # optional — unlocks Cloud mode

Then in your coding agent:

/ritual explore "Add multi-tenant RBAC"
/ritual build "Add notification preferences"

Two modes

	Light mode	Cloud mode
Setup	`ritual init`	`ritual init` + `ritual login`
Auth	None	Free Ritual Cloud account
Discovery questions	Local — saved to `RITUAL.md`	Generated by AI pipeline, reviewed in app.ritual.work
Recommendations	Inferred locally	Synthesized via the agentic pipeline
Collaboration	Solo only	Invite teammates to answer blocking questions

See CLI for the full mode comparison.

When to reach for which

Planning a feature — /ritual explore then /ritual brief. Run before writing code so the agent has the right questions answered up front.
Implementing against approved context — connect the MCP server, then call find_explorations and get_requirement_package before designing your approach.
Pre-PR check — /ritual gate to verify the implementation covers the Build Brief’s review-blocking items.
Rotating a key or onboarding a teammate — see API keys & scopes.