Ship ten starter templates, so a fresh install teaches the loop types

[scgopi]

A brand-new library is empty, and an empty ⌘T picker teaches nothing: the person who most needs to know what a Goal loop is for is exactly the person who has never written one. Templates are the natural place to explain the taxonomy, because a template can demonstrate a type rather than describe it.

The set

MAIN_LOOP.md orders the five types by how much you have to decide before the loop can start; the tour subtitles them by what makes them stop. These ten make that axis concrete by being it — the lesson is in each template's settings, not its prose.

Type	Templates	What the settings demonstrate
🩶 Main	Where does this live? · Why did this break?	No done check, no cadence — "I understood it" isn't checkable by a command
🔵 Goal	Get the build green · Review the diff on this branch · Raise test coverage	A check that decides · no check at all · a metric
🟠 Timed	Nightly dependency review (daily) · Watch the build (1h)	A brief worth repeating — and both follow their file
🟢 Turn	Port {area} to {target} · Pair on this	The two pause rhythms, side by side
🟣 Composite	Review, fix, verify	Three children and the two hand-offs between them

Two deliberate choices worth reviewing:

• Get the build green puts its token in the done check ({test_command}), not the brief. That means the most obvious starter isn't one-click — which is the point: filling it is what teaches that a Goal loop stops itself when a command says so, and that ⇥ walks every field a template left a hole in.
• Review the diff on this branch has no done check at all, so the pair with Get the build green teaches that the check is optional and finishing the work resolves the loop too.

How they ship

Real markdown files seeded into ~/.graphcode/templates, not constants — so the format teaches itself: open one and the front matter is right there.

• Once. Guarded by a .starters-seeded dotfile, so a starter you delete stays deleted rather than reappearing every launch.
• Never over anything. A file already at that name is somebody's, first run or not.
• Ids are fixed, so a loop following a starter keeps following it across a reinstall.

Where they show up

An empty canvas offers three — one Main, one Goal, one Timed, so the row climbs the commitment ladder — each labelled with what makes that type stop. One click opens the New loop dialog with the brief already applied.

         No loops in usage-cap yet
   [ Create Loop ]

   OR START FROM A TEMPLATE
  ┌────────────┐┌────────────┐┌────────────┐
  │▌Where does ││▌Get the    ││▌Nightly    │
  │ this live? ││ build green││ dependency │
  │ Main —     ││ Goal —     ││ Timed·daily│
  │ stops when ││ stops when │└────────────┘
  │ you close  ││ it's done  │
  └────────────┘└────────────┘

The ⌘T picker groups them under Starters — above All projects, below a project's own committed templates — until somebody saves a brief of their own. After that the scaffolding stops outranking their work and sorts in with everything else. PromptTemplate.isStarter rides in the file as starter: true, so the mark survives an edit and is visible to anyone reading the folder.

Verification

• Build succeeds; 1482 tests in 153 suites pass (up from 1467; 22 new)
• swiftlint lint — 0 errors. AppFeature was one line over its type-body budget, so onboardingDismissed's body moved to the trailing extension the way that file's own convention says to.
• swift format lint --strict — clean on every touched file

Not verified visually — no GUI automation here, so the starter row's layout on the empty canvas and the Starters group in the picker want a human eye.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MJR8Wuwc4qnaSBUMcYf7Af