Structuring UI Content
Quick start
Collect or infer:
- •Screen purpose and primary user task
- •All content elements (headings, body, labels, actions, help text)
- •User entry point and expected exit
- •Constraints (viewport size, scrolling behavior, accessibility requirements)
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- •Identify the primary task users complete on this screen.
- •List all content elements required to support that task.
- •Prioritize elements by: task criticality, temporal sequence, decision dependency.
- •Apply content hierarchy: primary action visible without scroll, supporting info near point of need.
- •Group related elements; separate unrelated elements with whitespace or dividers.
- •Validate reading order matches task flow and accessibility requirements.
- •Run the rubric check. Revise until it passes.
Degrees of freedom
- •Medium freedom: Structure principles are fixed; specific grouping and sequencing may vary by screen type.
- •Allowed variation: Visual hierarchy implementation (size, weight, position) may adapt to design system.
References
- •Templates: TEMPLATES.md
- •Rubric: RUBRIC.md
- •Examples: EXAMPLES.md