follow-our-standards

Follow our standards

A drift corrector for alignment to the consuming organization's engineering standards. 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 standards discipline.

Resolve the standards source

The authority is the consuming organization's own conventions; never work from recall of them. Resolve a readable copy per the method doc's ladder:

1. The consuming project declares its standards source. When the repo's own CLAUDE.md / .claude/rules/ names where the conventions live, a shared standards repository, a docs tree, a conventions directory. Resolve and read THAT. A local checkout is preferable to a remote fetch when one exists; a remote read (via the host's CLI or web tree) is the fallback.
2. No external source declared → the repo's own conventions. Read the conventions the repo carries itself. Its CLAUDE.md, .claude/rules/, CONTRIBUTING, docs, and re-anchor those.
3. Nothing declared anywhere → the portable baseline below.

State which source resolved so the citations are traceable.

Loading. Relevance-routed progressive disclosure

Do not load the whole convention set. Route through its own index. A top-level README or agent-instruction file, and pull only what the work in flight needs. Discover the applicable docs through that front door rather than hardcoding a doc map that will drift. Always re-anchor the core design principles; load a specific convention (testing, naming, error-handling, domain modelling, and the like) only when the current work touches it. When the repo you are working in declares its own design-doctrine docs, add them to the route set and load one when the work in flight is designing what that doctrine governs.

The principles this re-anchors