point-dont-copy

Point, don't copy

A drift corrector for pointer-over-copy discipline. The method, re-anchor, audit the work in flight, correct forward, report, and the tone that firing this is not an accusation, lives in ${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md. Read it; this file adds only what is specific to duplication discipline.

The discipline this re-anchors

Point at the living source; do not copy what it owns. This doctrine is already owned by convention docs. Re-anchor THEM, do not restate their content here. Resolve the source of truth per the method doc's ladder:

• Facts you own (in-repo). Your organization's reference-don't-duplicate convention. Every fact has one source of truth; consumers cite it by a stable anchor rather than restate it; literal versus semantic duplication; the describe / use / expose roles a file plays toward a fact.
• Facts an upstream owns (external). Your organization's documentation-and-citations convention. Cite the upstream and fetch it at read time; do not recap upstream-owned catalogs, schemas, flag inventories, or defaults into tracked files; place the citation at the sentence that defers to it; a stored external value needs a recheck trigger.

Read those where they live. When a consuming project declares none of them, re-anchor the portable baseline: provide a link or citation to the living source and never restate the facts it owns: a reworded paraphrase drifts exactly as a verbatim copy does, because both are a second copy that goes stale when the source moves.

This skill's own pins. Beyond what the conventions state

• Threshold two, not three. The reference-don't-duplicate smell signals fire at "three or more" occurrences; this skill pins the trigger at two, the second copy is already duplication to resolve by pointing, not something to tolerate until a third appears. A deliberate, tighter refinement (and a candidate change to that convention). Weigh a genuine case for local divergence on its merits, but the default at two copies is to consolidate to one source and point at it.
• Point at public contracts, not internals. Reference the stable public contract, a tool's invocation surface, the command and its arguments, never the internal script or file names behind it, which are rename blast radius that breaks every citation the moment they move. (The conventions cover citing stable anchors; this names the specific trap of citing an internal name where the public contract exists.)
• No capability enumeration. Phrase your OWN duties open-ended, not just upstream-owned inventories. A closed list of what something can do goes stale as the surface evolves; name current mechanisms only as clearly-marked examples. "mechanisms such as X and Y (examples, not a fixed list)", never as the definition.