← ClaudeAtlas

internal-shipped-referencelisted

Reviews a shipped-corpus edit for a reference that resolves only in this checkout and reads as portable, the one form the reference gate cannot classify by pattern. Use before shipping a change under claude/, docs/, governance/, scripts/, snippets/, standards/, or tooling/, routed here by `598-authoring-layout.md`. Do NOT use for a pull request number, a commit sha, a resolvable `docs/<name>.md` path, or a phase label, which `canon gate run`'s shipped-references stage already classifies by pattern.
erclx/canon · ★ 2 · Code & Development · score 68
Install: claude install-skill erclx/canon
# Internal shipped reference `src/shipped/references.ts` classifies four same-repository reference forms by pattern and stops there on purpose. Its own `DOCS_PATH` comment names the fifth: telling a `.claude/context/<name>.md` citation of this repository's own domain entry apart from an illustration of a target's own generic tree, such as `.claude/context/index.md`, is a semantic read no pattern makes. This skill is that read, plus the parallel judgment over a layout or count claim. ## Discriminator Read every added or changed line in the diff under this rule's eight corpora: `internal/`, `standards/`, `snippets/`, `claude/`, `governance/`, `docs/`, `scripts/`, `tooling/`. For each `.claude/context/<name>.md` token: - **Fine.** The sentence reads as an instruction for a target session to consult its own project's copy if one exists, or illustrates the path shape a target's own tree would take, never naming a fact only this checkout holds. `ux-measure/SKILL.md`'s `.claude/context/development/: the documented run commands and the port each serves` is this case, read as "check your own project's entry." - **Fails.** The sentence names a fact true of this repository specifically, one only this checkout's own `.claude/context/` resolves, such as a documented decision or a domain narrative a target reader cannot open. `canon-cli/SKILL.md`'s prior citation of `.claude/context/tooling.md` as "the toolkit's" was this case. Do not test a token against what a scaffolded project's