base-in-reality

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY in this skill are to be interpreted as described in BCP 14 (RFC 2119, RFC 8174) when, and only when, they appear in all capitals.

A read-only, research-grounded repository audit. It answers one question for each notable design decision in a repo: does this violate an established norm, standard, algorithm, or best practice — provably, against a real source?

The defining rule: no fabricated authority. Every finding MUST be tied to a source the agent actually fetched in-session. Ungrounded claims MUST be reported as UNCONFIRMED, and MUST NOT be reported as violations, because a violation with no fetched source is fabricated authority.

When to use

Use when you want to sanity-check a codebase, architecture, or business logic against the state of the art and against domain standards — e.g. "is our APR calculation correct per lending norms?", "does our crypto follow NIST?", "is this consensus approach sound?", "does our ML eval avoid known leakage pitfalls?". Works on any repo; adapts to its domain(s).