docs: re-center on standalone compose; demote init.sh to dogfood#66
Merged
Conversation
The docs led with the up.sh-subfolder / init.sh model as if required. With the compose file now self-sufficient, re-center on the standalone path and frame init.sh as the dogfood-only convenience it now is. - README intro + TL;DR lead with `docker compose up` in your own project (no clone/build/init.sh); the workflow steps drop the `mkdir cv` subfolder model. - Rename "Run commands" → "Local development & dogfood" with explicit demotion; the up.sh/init.sh/.env mechanics live there. - "How it fits together" gains a bullet: the image bakes the workflow in (~/.claude/commands + skills), groundwork for in-container driving while Claude still runs on the host today. - .env.example reframed as OPTIONAL overrides (compose fallbacks cover a bare up). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
The docs were misaligned — they led with the
up.sh-subfolder /init.shmodel as if it were required, even though the compose file is now self-sufficient (#65). This re-centers on the standalone path.Changes
docker compose upin your own project — no clone, no local build, noinit.sh. The workflow steps drop themkdir cv"project = subfolder under this repo" model.up.sh/init.sh/.envmechanics now live there, framed as the dogfood convenience (per-project container naming).~/.claude/commands+~/.claude/skills, ADR-0017) — honest that Claude still drives from the host today, with that as groundwork for in-container driving..env.examplereframed as OPTIONAL overrides (compose fallbacks cover a bareup), instead of "generated by init.sh — copy to .env".Not changed (deliberately)
init.shanddevcontainer.json'sinitializeCommandstay — they're correct for the dogfood / VS Code path. This is a docs-alignment pass, not a removal.Docs-only. All internal anchors verified (heading rename introduced no broken links).
🤖 Generated with Claude Code