Conciseness

The body is dense imperative guidance with no padding or explanations of concepts Claude already knows — e.g., "Ordinary JSON parsing silently discards duplicate keys" is a one-clause justification for a manual check, not a tutorial. Every line carries an instruction, matching the lean anchor-5 profile.

Actionability

Guidance is highly concrete — named paths and tests (`src/lib/i18n/locales.ts`, `catalogs.spec.ts`, `e2e/translation-loading.test.ts`) plus one copy-paste command (`mise x -- pnpm --filter chatto-frontend exec vitest run --project server src/lib/i18n`) — but falls short of fully copy-paste-ready since the rg search patterns and the duplicate-key detection method are left implicit.

Workflow Clarity

A clear five-phase sequence (Establish scope → Run existing checks → Inspect catalogs → Inspect production call sites → Fix and verify) with explicit validation and feedback loops: "Run the focused i18n suite again after fixes", type checks, the build's `check:i18n`, and browser verification with a stated fallback ("If browser verification is unavailable, state the gap").

Progressive Disclosure

The single 100-line file is well organized under clear section headers with no bundle references to split, and the content is appropriately self-contained for an audit workflow; it sits just below anchor 5 because the dense catalog-inspection checklist could eventually merit a separate reference file, and the body exceeds the under-50-lines simple-skill bar.

Specificity

"Audit and clean up" plus five enumerated areas ("catalog integrity, untranslated UI text, regional overrides, locale formatting, and RTL behavior") lists several concrete capabilities, but only two primary action verbs — just short of anchor 5's multiple distinct actions, and clearly above anchor 3's 1-2 actions.

Completeness

It clearly answers "what" ("Audit and clean up Chatto frontend internationalisation, including catalog integrity...") and explicitly answers "when" with concrete trigger phrases ("Use for an i18n hygiene pass or a focused translation audit"), matching the anchor-5 pattern; not anchor 4, whose "when" is less explicit.

Trigger Term Quality

Natural keywords are present ("i18n", "internationalisation", "translation audit", "locale", "RTL") with explicit triggers ("Use for an i18n hygiene pass or a focused translation audit"), but common user-side variants such as "localization", "l10n", or "translate strings" are missing.

Distinctiveness Conflict Risk

The description is scoped to a named product and domain ("Chatto frontend internationalisation") with distinct triggers, giving it a clear niche and minimal overlap with generic translation or frontend skills.