reuse-or-replacelisted

Re-anchor the anti-fragmentation discipline that when an established way of doing something already exists — a code idiom, structure, error-handling approach, naming shape, doc format, or process — new work REUSES that established way or openly REPLACES it (migrate the old uses, record the decision); it never silently stands up a second, parallel way alongside. Then audit the work in flight for an invented approach that diverges from an established way with no stated reason. Replacing the established way is first-class — when evidence backs an improvement, or its rationale is missing, incumbency-only, or stale — the sin is the SILENT second way, not divergence itself. Use when: 'reuse or replace', 'we already have a way of doing this', 'don't invent a second way', 'keep it one way', 'follow the existing pattern or replace it', 'be consistent', 'you added a parallel way', 'this diverges from how we do it elsewhere', or at conversation start on work that extends an established codebase, structure, or process.
melodic-software/claude-code-plugins · ★ 13 · AI & Automation · score 79

Install: claude install-skill melodic-software/claude-code-plugins

# Reuse or replace A drift corrector for anti-fragmentation discipline: one way to do a thing, not two. When an established way already exists, new work reuses it or openly replaces it — it does not add a silent second way beside it. 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`](../../context/re-anchor-audit-correct.md). Read it; this file adds only what is specific to reusing or replacing an established way rather than splitting into a parallel one. ## The discipline this re-anchors When a codebase, structure, or process already has an **established way** of doing something, new work must not silently stand up a **second, parallel way** beside it. Two coexisting ways of doing the same thing is fragmentation — it splits the reader's model, doubles the surface that drifts, and taxes every future change with a "which one?" decision. Resolve the source of truth per the method doc's ladder: if the consuming project states a consistency / one-way rule in its own `CLAUDE.md` / `.claude/rules/`, re-anchor THAT. Otherwise re-anchor this portable baseline. Facing an established way, new work has exactly **two honest options** — the two this skill is named for: - **Reuse it.** Follow the established way, so the codebase keeps one way. - **Replace it.** Openly argue the established way should change, then — if it should — *migrate