docs: the three modes and /goal in the README, each under its own banner - #159
Merged
Conversation
Four SVG banners in the hero's visual language — build, plan, design, and /goal — and two sections: Modes (what each agent may touch, one Tab apart) and Goal (the syntax with its fields, what the gates and the judge do at the end of a turn, the budget, pausing and the slash commands). The prompt footer's latency and tokens-per-second get a line under Use. Claude-Session: https://claude.ai/code/session_013JrKXL4pdgTu2EtCjgiYyq
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
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.
Four banners in
docs/modes/drawn in the hero's language (same gradient, grid, glow and monospace; one accent each — brand red for build, blue for plan, the review page's gold for design, violet for/goal), and two new README sections:Tabcycles the three primary agents; what build, plan and design may each touch, and where each hands off (plan_exit,design_exit). Design links to the existing tutorial./goalsyntax with its fields (outcome,verify,gate,constraints,stop when), what happens at the end of every turn (gates, the DONE / CONTINUE / BLOCKED / WAIT judge,goal_complete), the 20-turn budget, pausing onCtrl+Cand on a new process, the slash commands, andexperimental.goal.Plus one line under Use for the prompt footer's latency and tokens-per-second.
https://claude.ai/code/session_013JrKXL4pdgTu2EtCjgiYyq
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.