Visual Hierarchy Blueprint
Establish clear visual hierarchy through size, weight, color, and spacing so users can quickly scan and understand interface priority without cognitive overload.
| Feature | visual-hierarchy |
| Category | UI |
| Version | 1.0.0 |
| Tags | design-system, accessibility, visual-design |
| YAML Source | View on GitHub |
| JSON API | visual-hierarchy.json |
Fields
| Name | Type | Required | Label | Description |
|---|---|---|---|---|
primary_content | text | No | Main content user came to interface to interact with | |
secondary_content | text | No | Supporting information or metadata | |
tertiary_content | text | No | Additional details, help text, or background info | |
hierarchy_levels | number | No | Number of distinct visual hierarchy tiers in this interface (typically 3-5) |
Rules
- not_all_elements_equal: Not all elements should be equal — differentiate primary content from secondary
- use_size_strategically: Use size strategically — scale is the most powerful hierarchy tool after careful spacing
- no_grey_on_colored_backgrounds: Don’t use grey text on colored backgrounds — reduces contrast and harm accessibility
- emphasize_by_deemphasizing: Emphasize by de-emphasizing — make less important elements quieter, not primary ones louder
- never_use_labels_as_primary_identity: Never use labels as primary identity — labels are a last resort after visual hierarchy fails
- separate_visual_from_document_hierarchy: Separate visual hierarchy from document hierarchy — visual and structural order needn’t match
Outcomes
User_scans_interface (Priority: 1)
Given:
- user scans interface for key information
Then:
- primary actions and content are visually distinct through size, weight, or color
- secondary elements are de-emphasized through reduced opacity, weight, or color intensity
- all elements have clear visual relationships expressed in spacing and contrast
Result: user can scan interface in under 2 seconds without reading labels
Interface_has_multiple_sections (Priority: 2)
Given:
- interface has multiple content sections
Then:
- section headings use significantly larger type size than body content
- heading weight (font-weight) is proportional to hierarchy level
- spacing between hierarchy levels increases as importance decreases
Result: visual structure is immediately apparent without visual stress
Critical_element_needs_attention (Priority: 3)
Given:
- action or data point is critical to task completion
Then:
- set_field target:
element_sizevalue:largest in context - set_field target:
color_saturationvalue:highest in context - set_field target:
contrast_ratiovalue:>=7:1
Result: critical element has no visual competitors for user attention
Low_priority_content_present (Priority: 4)
Given:
- interface has low-priority metadata or supporting info
Then:
- set_field target:
text_colorvalue:reduced_saturation or opacity < 100% - set_field target:
font_weightvalue:lighter than body - set_field target:
element_sizevalue:12-14px for web
Result: low-priority content is accessible but won’t distract from primary content
Related Blueprints
| Feature | Relationship | Reason |
|---|---|---|
| typography-system | recommended | Type scales and font selection enforce hierarchy through size relationships |
| spacing-system | recommended | Spacing reinforces visual hierarchy through whitespace and grouping |
| color-system | recommended | Color, saturation, and contrast tools for visual differentiation |
| accessibility | required | Visual hierarchy must maintain sufficient contrast for WCAG AA compliance |
AGI Readiness
Goals
Reliable Visual Hierarchy
Establish clear visual hierarchy through size, weight, color, and spacing so users can quickly scan and understand interface priority without cognitive overload.
Success Metrics:
| Metric | Target | Measurement |
|---|---|---|
| success_rate | >= 99% | Successful operations divided by total attempts |
| error_rate | < 1% | Failed operations divided by total attempts |
Autonomy
Level: semi_autonomous
Tradeoffs
| Prefer | Over | Reason |
|---|---|---|
| accessibility | aesthetics | UI must be usable by all users including those with disabilities |
Coordination
Protocol: request_response
Consumes:
| Capability | From | Fallback |
|---|---|---|
accessibility | accessibility | degrade |
Safety
| Action | Permission | Cooldown | Max Auto |
|---|---|---|---|
| user_scans_interface | autonomous | - | - |
| interface_has_multiple_sections | autonomous | - | - |
| critical_element_needs_attention | autonomous | - | - |
| low_priority_content_present | autonomous | - | - |