Handbook
Tutorials — 301 (overview)
301 content assumes 201 habits are in place and you are comfortable losing a throwaway session.
Updated
Prerequisites
- Keep Wizard 201 + Studio 201 habits fresh (reviews, checkpoints, reversible exports).
- Read Experimental surfaces so you recognize feature-flag divergence.
301 content assumes 201 habits are in place and you are comfortable losing a throwaway session.
| Guide | Time (typ.) | Outcome |
|---|---|---|
| Studio 301 | 25–35 min | Navigate advanced Studio surfaces without breaking context |
| Wizard 301 | 20–30 min | Coordinate bundles, refine, and review passes |
| Artifact bundles | 15–20 min | Shape exports for downstream tooling |
| Refine | 20–30 min | Tighten assumptions with structured prompts |
| Review / recheck | 15–25 min | Validate outputs before handoff |
Studio subsite (301 depth)
Pair Studio 301 with the atlas and focused pages: Studio route atlas, Navigation and shell, Workspace and projects, LLM and Fleet settings, Docs Health UI.
Experimental surfaces
Some 301 flows depend on feature flags or optional LLM gateways. Callouts in each chapter mark experimental behavior — treat those steps as best-effort until your build matches the documented flag matrix in Configuration reference.
When to escalate
If Studio is blank, assets 404, or Wizard sessions fail to persist, start at Troubleshooting before assuming a methodology issue.
Recover
Turn off experimental gateways, reconcile .lenses-local/ checkpoints against Security and local-first, then resume from Wizard 301 once the workspace root matches your intent.