| name | mode |
| description | Switch how much application code the AI writes for dinotable — between guided (Zoha writes all code), collab (split), and autopilot (AI writes the frontend, Zoha drives the guided core). Use when Zoha says "set mode to X", "switch to autopilot", "let me write it myself", "just build the web app for me", or asks what the modes are. |
Switching the dinotable mode
The mode is the dial for how much app code the AI writes. Full definitions:
docs/MODES.md. The active mode lives in one place — the **Active mode:**
line near the top of AGENTS.md (Prime directive — the mode dial). Every
per-tool file defers to it, so editing that one line changes behavior in every
tool and agent.
Steps
- Read the current mode from the
**Active mode:** line in AGENTS.md.
- Confirm the target (
guided | collab | autopilot). If Zoha didn't
name one, ask which, and give the one-line trade-off of each from
docs/MODES.md.
- Confirm the trade-off in one line, e.g. "autopilot: I write the frontend
apps and narrate decisions; you review, drive, and commit — the backend core
stays guided."
- Update the single source of truth: edit the
**Active mode:** line in
AGENTS.md to the new mode and re-stamp the date. Do not scatter the mode
into other files — they all read this one line.
- Confirm the new rules in chat: what the AI will and won't write now in
both zones (frontend vs guided core), and restate the invariants that never
change — Zoha makes all commits, ADRs are Zoha's, work is still planned as
milestone docs.
Guardrails
- This skill only flips the dial and explains it. It does not start writing
code, begin a milestone, or solve challenges — wait for Zoha to direct what's
next.
- The zone split is fixed by
docs/MODES.md: even in autopilot, the guided
core (apps/api, libs/**, the reservation engine, AI search, infra/**) is
never written by the AI. Autopilot only frees the frontend zone (apps/web,
apps/back-office, apps/mobile).
- Never change commit or ADR ownership — those are Zoha's in every mode.
