docs(core): point generated Claude notes at skills, not path-glob rules - #19
Merged
Conversation
The generated CLAUDE.md told every consumer to reserve .claude/rules/*.md for path-glob injections. The pattern that actually holds up is a skill carrying the procedure plus a scoped CLAUDE.md pointing at it, which loads where the work happens. Also drops 'rule file' from the module-target error, which steered readers to the same mechanism while explaining an unrelated mistake.
ApprovabilityVerdict: Approved d508947 Documentation-only changes updating guidance text in generated files and one error message string. No runtime behavior or logic changes. You can customize Macroscope's approvability policy. Learn more. |
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.
Every generated
CLAUDE.mdcurrently tells the consuming repo:The pattern that holds up better is a skill carrying the procedure or standard, plus a scoped
CLAUDE.mdthat points at it — the slice auto-loads in the directories where the work happens, and the depth lives in the skill rather than being injected wholesale on every file touch. The generated note now says that.Also drops "rule file" from the module-target error in
config.ts. It steered readers toward rules while explaining an unrelated config mistake (a module declaring a non-root target).Rules remain fully supported —
claudeRulesDir,claudeRuleFile, andclaudePathsare untouched. This only changes what the kit recommends in generated output.examples/listforge-likeregenerated with the CLI.examples/gauntletwas hand-edited on the same line because that fixture currently fails to build for an unrelated reason (010-overview.mddeclares targetapi, and modules only compose into the root output) — worth a separate fix.223 tests pass. Pre-existing prettier warnings on the touched files are left as they were rather than reformatting 114 files in this PR.
Note
Update generated Claude notes to reference
.ai/skills/*instead of path-glob rulesrender.tsso generatedCLAUDE.mdfiles now direct users to put procedures in.ai/skills/*and reference them from a scopedCLAUDE.md, replacing the old advice to use.claude/rules/*.mdfor path-glob injections.gauntlet/CLAUDE.mdandlistforge-like/CLAUDE.mdto match.config.tswhen a module targets a non-root scope to say "its own file" instead of "a rule file".Macroscope summarized d508947.