Handbook

Tutorials — 101 (overview)

Beginner paths assume Install and run is complete and the server answers on loopback.

Updated

Prerequisites

  • Finish Install and run so python3 -m lenses listens on localhost.
  • Have a disposable repo or clone you can inspect through Studio/Wizard surfaces.

Beginner paths assume Install and run is complete and the server answers on loopback.

Guide Time (typ.) Outcome
Studio 101 5–10 min /studio/ loads; you complete one navigation path
First Classic dashboard 5 min Classic / loads; you review one useful Classic view
First Docs Health scan 2–5 min Summary and work-items (GET-only) make sense for your workspace
Wizard 101 15–25 min Create or resume a Wizard session; understand hub vs session URLs

Verify (101 lane)

  • Each linked tutorial above loads without maintainer-only banners for audience: public builds.
  • You can articulate one observable artifact after each row (Studio chrome, Classic dashboard snapshot, Docs Health summary row, Wizard session JSON).

Studio IA (optional reads)

Page Why open it
Studio route atlas Canonical /studio/... token checklist
Studio — navigation and shell Header, sidebar, route families
Studio — troubleshooting Blank shell / wrong API origin

Suggested order

Suggested order

  Lane A ──► handoff ──► shared outcome
  Lane B ──► inspect / adapt ──► feedback
Either lane can start first; both assume install is done

Recover

When installation fails, rerun the Prerequisites checklist, then escalate through Studio troubleshooting before assuming a Wizard-specific bug.

Scenario (no secrets)

You cloned forge-lenses beside your product repo, started the server, and want one win today: either see Studio chrome and a project row, or create a throwaway Wizard session to learn the twelve-step UX — without connecting a real LLM if you are offline.

Next ladder

When 101 feels comfortable, open Tutorials — 201 for daily habits and Wizard 201 flows.