Conciseness

A dense, lean rules digest where nearly every token is rule content ('Allowed: `flowchart TD`, `graph TB`. Forbidden: `LR` / `RL` directions') with no padding explaining concepts Claude already knows; however time-sensitive specifics outside a deprecation section ('operator decision 2026-08-17', 'operator decision 2026-08-18', 'card t47') warrant a minor penalty, keeping it at anchor 4 rather than 5 — though stale facts are properly quarantined in the Known-Stale section.

Actionability

Rules are concrete and largely executable — exact canonical-chain table, correct/wrong emphasis examples ('Correct: `**바이브코딩** (Vibe Coding)` — parenthetical OUTSIDE the markers'), icon shortcode syntax, and redirect path patterns — but there is no full vercel.json snippet and the checks are delegated by name ('run the inlined checks in Skill("hns-oss-docs-verify") instead'), so it fits anchor 4 rather than the fully copy-paste-ready anchor 5.

Workflow Clarity

The rules are clearly numbered and organized but there is no step sequence for the 4-locale batch edit obligation, and validation is only delegated by reference ('The verify recipe's version-string check (Skill "hns-oss-docs-verify" §6) enforces this at the exit gate') rather than inlined as checkpoints — matching anchor 3 ('checkpoints missing or implicit'), and the batch 4-locale/deploy context without explicit validation steps caps it at 3.

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the body is self-contained with a clearly signaled one-level-deep SSOT pointer at the top ('SSOT: `.moai/docs/docs-site-i18n-rules.md`') plus a dedicated stale-facts section — good structure matching anchor 4; minor gaps (cross-skill references by name only) keep it below the fully well-signaled anchor 5.

Specificity

Enumerates many specific covered items ('canonical-locale chains, the 4-locale same-PR obligation, Mermaid TD-only, the no-emoji + icon-shortcode rule, emphasis-marker spacing, the URL blacklist, version SSOT, vercel.json redirect pattern, and the immutable Vercel binding'), but lists topics covered rather than concrete executable actions, so it fits anchor 4 rather than 5 and is clearly above anchor 3's 1-2 actions.

Completeness

The 'what' is clear (a HARD i18n rules digest covering nine enumerated rules) and the 'when' is explicitly present ('Loaded FIRST by every oss-docs specialist before any edit'), so it avoids the missing-trigger cap of 3; however the trigger is a load-order directive for specialists rather than a concrete user trigger phrase, keeping it at anchor 4 rather than 5.

Trigger Term Quality

Contains good natural domain keywords ('i18n', 'README', '4-locale', 'docs-site', 'Mermaid', 'Vercel', 'emoji', 'URL blacklist') that a contributor on this repo would say, but coverage is heavy on project-specific jargon ('oss-docs harness specialists', 'adk.mo.ai.kr') and misses common synonyms like 'translation' or 'localization', placing it at anchor 4 rather than 5.

Distinctiveness Conflict Risk

Scoped to the 'moai-adk-go README 4-locale set and the docs-site (adk.mo.ai.kr)' — a clear niche with distinct triggers and minimal conflict risk with any general skill, matching anchor 5.