You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
README restructured to lead with concepts, not commands. The v0.1.21 README jumped straight into the install tier table + 3 install commands before explaining what the OS is, what a "skill" is, or what /bootstrap does. Fork users landed on a wall of shell commands without context. New structure:
What is this? (concept first)
How it works — new section explaining the three layers (skills / PARA workspace / Configuration tokens) and the two-stage setup model (shell install.sh for power-user toolchain, Claude /bootstrap for personalization)
Install — now framed as "you're trying to reach /bootstrap; everything else is plumbing." Path A (Minimal) is clone → cd → claude → /bootstrap; Path B (Lite CCv4) adds ./scripts/install.sh --no-fastedit-model before claude; Path C (Full) drops the flag.
The PARA workspace — explains each of the 5 folders (0-Inbox, 1-Projects, 2-Coding, 3-Resources, 4-Archive) with a "what goes in it" + "why it exists" column. New callout that /bootstrap creates the empty folder skeleton; skills own the content.
/bootstrap reframed as the central setup step. Previous README treated install.sh and /bootstrap as equally-weighted install steps. The new framing: /bootstrap is THE step that personalizes the OS to you; install.sh is optional plumbing that only matters if you want /research, /autonomous, /premortem, /review. Minimal-tier users skip install.sh entirely.
Notes
README-template.md grew from 438 → 482 lines (+44, mostly the new "How it works" section).
No skill bodies, hooks, or scripts changed in v0.1.22 — README-only release.