ritual

Ritual dApp development begins by typing /ritual to classify your intent and route the session to the correct agents. This accelerates onboarding by enforcing a checkpoint-driven workflow with a `.ritual-build/progress.json` file.

The Ritual workflow routes and manages dApp development sessions by classifying user intent into build, learn, or debug paths. It enforces a strict skill unit contract using a SKILL.md file with YAML frontmatter for deterministic agent routing.

Yes, a SKILL.md file is required at the root to enforce a strict skill unit contract. It must contain YAML frontmatter with the name and description fields to successfully initialize and route your Ritual dApp session.

Ritual manages deterministic session progress using a `.ritual-build/progress.json` checkpoint file. This ensures that your dApp build phases remain resumable, allowing you to pick up exactly where you left off during development.

Yes, you can debug issues with your existing dApp architecture. The system classifies your intent and routes you to the correct agents and sub-skills to diagnose problems and provide guidance on Ritual-chain protocol references.

A resources directory is an optional component supported by the Ritual workflow. It allows you to organize supplementary files and references alongside the required SKILL.md to guide checkpoint-driven progress through your dApp build.