Visual Hierarchy

Establish clear importance through size, weight, color, and spacing. Every screen should have one obvious focal point — the primary action or content the user came for.

  • One primary action per screen — there MUST be a single focal point; if everything is bold, nothing is bold
  • Use size and weight (not just color) to distinguish heading levels
  • Group related content with proximity; separate unrelated content with whitespace
  • Interactive elements MUST be visually distinguishable from static content
  • Disabled elements SHOULD be visually muted but still discoverable

See agenticdevelopercookbook://guidelines/implementing/accessibility/accessibility for accessibility requirements (contrast, labels, focus order).

References:

version
1.0.3
platforms
windows
tags
ui, visual-hierarchy
author
Mike Fullerton
modified
2026-06-09

Change History

Version Date Author Summary
1.0.3 2026-06-09 Mike Fullerton Repair stale cross-reference link scheme
1.0.2 2026-04-09 Mike Fullerton Add trigger tags
1.0.1 2026-04-09 Mike Fullerton Reorganize into use-case directory
1.0.0 2026-03-27 Mike Fullerton Initial creation