gold-standardlisted

# Gold Standard **Language:** Generate EVERYTHING at runtime in the user's language — questions, answer options, menu labels, recommendations, report narrative. Detect from their messages; never default to English just because this file is English. English is allowed only for technical terms: commands, paths, code identifiers, severity labels (CRITICAL/HIGH/MEDIUM/LOW), and tier names (Light/Standard/Heavy). Answer: **"For a project that does THIS — are rules/standards/features 100% vs world-class? If not, what's missing?"** Four acts: **AUDIT** → **FILL** → **ADOPT** → **CONFORM**. Stop at any. ## Triggers | Keyword | Act | |---|---| | "audit rules" / "gold-standard" / "are we world-class" | AUDIT | | "fill gaps" / "complete our rules" | FILL | | "work by these rules" / "follow from now on" | ADOPT | | "conform old code" / "retrofit" | CONFORM | | "fill and adopt" / `ACTION=fill-adopt` | AUDIT → FILL → summary → ADOPT → offer CONFORM | ## Acts ADOPT and every CONFORM fix are gated through `ask_question` — never assume approval. 1. **AUDIT** — pick 3–5 named exemplars **fresh at run time** (the bar moves with the era — never reuse a remembered bar), derive the 100% checklist per dimension, score (✅/🟡/❌/N-A), give overall %. Previously filled/adopted rules are audit subjects too: a rule past its `revalidate` due date or contradicted by today's exemplars is a gap. 2. **FILL** — write missing MUST-HAVE rules into project's rules home (`.claude/rules/` → `AGENTS.md` → `ST