What tutorials are for
Guides answer a single "how do I…" question in isolation. Tutorials go the other way: they take a complete real-world scenario and walk you through every rousseau piece needed to ship it. Every tutorial produces something you could paste into your own workspace and expect to work.
| Tutorial | You end up with |
|---|---|
| Build a code-review bot | A Slack channel where mentioning @rousseau on a repo path triggers a read + grep review pass. |
| Nightly changelog | A cron job that summarises the day's git log and pushes it to WhatsApp at 18:00. |
| Deploy to a VPS | A hardened rootless-Podman deployment on a fresh VPS behind systemd. |
| Expose tools via MCP | Claude Desktop driving rousseau_search_sessions, rousseau_list_sessions, rousseau_read_session, rousseau_cron_list. |
| Harden the approver | A strict pattern-mode approver with default: deny, validated by the slog audit trail. |
Prerequisites
Every tutorial assumes you have completed the Quickstart: rousseau is on $PATH, a provider is configured, and rousseau chat produces a response.
Beyond that, individual tutorials call out anything extra — a Slack workspace, a VPS, a WhatsApp-linked number, or claude desktop.
Not a tutorial
If you want a short "how do I do X" recipe, read Guides. If you want the exact CLI flag or config field, jump to Reference. If you want to understand what a piece of rousseau does before wiring it up, start with Concepts.