What problem does it solve? Repositories that document themselves in two languages drift apart silently: numbers diverge, translations go stale, and readers of one language act on facts the other language contradicts. This Skill defines the pairing rules, README routing, and verification checks that keep both surfaces stating one set of facts. ## Core Features & Use Cases - Pairing and routing rules: Establishes which surface takes the bare filename per artifact class, requires mutual links between paired documents, and keeps the README as a router rather than a second statement of facts. - Verifiable numbers: Enforces that every number in a document names the command that prints it, so any reader can refute a stale figure in one line. - Divergence detection and honest stubs: Uses structural comparison, source_sha256 stamps, and skeleton checks to catch drift, and publishes explicit stub pages instead of machine drafts passed off as translations. - Use Case: A repository ships README, docs, and specs in English and Russian. Use this Skill to audit the pair inventory in both directions, execute every command a document names against its printed number, and report coverage split by translated, machine-drafted, stubbed, and absent. ## Quick Start Use the bilingual-documentation skill to audit this repository's paired documents and README routing, then report what diverged between the two languages.
