Repository navigation
docs(tutorial): outcome hero, core/rest syntax split, one "how to run" home - #6
Merged
Merged
Conversation
…" home Tutorial (docs/index.html): - Hero: replace the good-vs-bad comparison with a single outcome-in-motion terminal — the loop self-correcting fail → reflect → green → gated PR — with the .loop that drove it below. New "Stop babysitting the agent" framing. - Syntax split: TOC regrouped into "Core syntax · the five decisions" and "The rest of the syntax"; #what names the core/rest cut; new #beyond section catalogs the non-core constructs (compose / augment / ops) with reference links. - One "how to run" home: a 3-way chooser (write by hand in VS Code · run in Claude Code [recommended] · run headless via the CLI), VS Code consolidated into a single #running-vscode subsection (was documented twice, inconsistently), getting-started trimmed to a pointer. runMode standardized on ask/session/output. Keyword reference (docs/keywords/): - Recut into two tiers (Core syntax / The rest) with re-sorted groups; detail-page category badges synced (Core syntax / Compose / Augment / Human / Ops & reuse). - Add the missing use-skills + remember-in pages and cards (0.4.0 constructs). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Replace the animated terminal with a static, auto-height full run trace so there's no oversized empty box (the fixed 330px pane left dead space). Drop the now-unused animation script. - Remove the Workshop / LoopFlow Lab links from the hero lede so it doesn't push readers out of the tutorial before they start (still linked from Getting started and the TOC). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
# Conflicts: # docs/index.html
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reorganizes the tutorial and keyword reference around three asks.
1 · Hero — show the power, not a comparison
Replaces the good-vs-bad hero (messy Claude session vs a clean
.loop) with a single outcome-in-motion terminal — the loop self-correcting✗ fail → reflect → edit → ✓ green → ⛐ gate → PR #128, never main— and the one.loopthat drove it just below. New framing: "Stop babysitting the agent."2 · Split the syntax into core + the rest
#whatnow names the split (these five are the engine; everything else composes or configures).#beyondsection catalogs the non-core constructs — Compose / Augment / Ops & reuse — each linking to its keyword page.use skills+remember inpages + cards (shipped in 0.4.0, never documented here).3 · One "how to run" home
#running-vscodesubsection; getting-started trimmed to a pointer;loop.runModestandardized onask/session/output.Verification
<section>/<table>/<ul>balanced;vscode-optionalgone,runModementioned once.Docs-only; no
packages/changes (the VS Code 0.4.0 work is PR #5).🤖 Generated with Claude Code