docs: add overlay creation guidance#16
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dlovell
force-pushed
the
docs/overlay-guide
branch
from
b3f4a66 to
41b5169
Compare
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.
Summary
CLAUDE.md: preferuv sync --group devover legacy--devwhen targeting a specific group, and strip inherited dead weight when creating overlaysprojects/README.mdwith guidance on creating new overlays: start from closest existing overlay, cargo volume topology (shared vs per-worktree),external-volumes.txtregistration, and artifact-gated build stepsFollow-up from #14 (batchcorder overlay) — documents learnings from that process for future overlay authors.
Test plan
🤖 Generated with Claude Code