USING UXDLIn development
Generate UXDL from Product Intent
Generate candidate flows while preserving visibility over assumptions, unknowns, and conflicts.
Generation Philosophy
UXDL generation should help structure product intent, not make unreviewed product decisions on the user's behalf. UXDL prefers an explicit 'Unknown' marker over a plausible but unsupported Screen, State, Action, or Relation.
4 Generation Confidence States
Candidate generated elements are categorized into four explicit states:
- Confirmed — Directly supported by input source text or human confirmation.
- Inferred — Plausible interpretation requiring explicit human visibility.
- Unknown — Required information missing in input requirements.
- Conflict — Input sources explicitly disagree on intended product behavior.
Human Acceptance Workflow
Generated UXDL remains a candidate artifact until the author reviews inferred branches, resolves unknown questions, and accepts the specification into the canonical behavioral model.