project-legibility

Check early design or implementation-planning direction for fit with user/domain purpose, explicit constraints, current evidence, and verifiable success conditions before existing code, copied behavior, fallback/default logic, or shortcut pressure shapes the design. Use when reuse/precedent, rejected constraints, meaning-affecting fallback, or "copy now, clean later" could steer design. Skip mechanical edits, read-only owner discovery, clear specialist cases, and coding after direction is settled.

Use when a concrete document, documentation diff, or explicitly selected documentation package needs final wording or document-level cleanup such as distinct roles, reader routes, current-vs-stale separation, and one owner per current decision, contract, gate, or plan. Stay within the selected documentation scope; do not choose external source truth, design task state, or change implementation meaning.

Use when cross-layer feature, migration, integration, port, refactor, review, bug fix, or design planning needs one owner for user/domain meaning across UI, route, client state, command, API, storage, realtime, adapter, or presentation layers. Trigger for identity aliases, lifecycle/status, permissions/capabilities, route/query grammar, command payloads, result/event projection, freshness/fallback/revision semantics across representations, compatibility translation, duplicated meaning rules, or multiple representations of the same user/domain meaning. Do not use for read-only owner discovery, local flow cleanup after owners are clear, pure async responsiveness/freshness work, or scope-control alone.

Use for read-only source-of-truth audits: identify the current code, API, config, doc, or behavior to follow; compare a proposed, migrated, ported, or current change against it; and report evidence, mismatches, unresolved decisions, and owner-level recommendations.