Back to Overview
QUALITYAvailable

Contextual Linter

Advisory heuristic checks evaluating whether standard user flow expectations are present.

Linter Pipeline Architecture

Flowchart
Rendering diagram...
Contextual linter operates downstream of structural reference validation.

5 Core Contextual Checks

The shipped contextual linter runs 5 precision checks:

  • 1. State Coverage (state_coverage) — Stateful actions (submit, save, pay, login) must have an error/failed branch.
  • 2. Dead Ends (dead_end) — Non-terminal screens must have at least one outgoing action unless metadata.terminal is true.
  • 3. Recovery Paths (recovery) — Error states must provide an outgoing action for user recovery (retry, go back).
  • 4. Guard Conditions (guard) — Irreversible actions (delete, cancel, revoke) must declare a 'when' guard condition.
  • 5. Empty States (empty_state) — Screens displaying dynamic data lists must declare an 'empty' state.

Phase 2 Screen Archetypes

metadata.archetype is a proposed direction for replacing linter heuristics with explicit screen nature contracts (e.g. public_static, data_view, auth_flow, form_input, sensitive_transaction).