docs: establish adaptive visual design gates

2026-06-11 02:17:44 +08:00
parent d35d1159b7
commit 47d3b1a6fe
1 changed files with 27 additions and 0 deletions
@@ -16,6 +16,33 @@ Every screen and feature should strengthen this loop. Generic feature accumulati
 ## Design Principles
 ### Five Acceptance Requirements
 Every design decision must pass these five product-level requirements:
 1. Dynamic data and state resilience
   - Design components for changing content, item counts, asynchronous feedback, lifecycle restoration, and navigation state.
   - Validate behavior with empty, normal, dense, long-content, loading, error, active, paused, completed, and restored states.
 2. One coherent visual system
   - Use a consistent grammar for color, type, shape, spacing, depth, iconography, illustration, and motion.
   - Permit limited visual contrast only when it explains a meaningful state, mode, reward, warning, or transition.
 3. Clear structure and interaction
   - Layout must explain what is interactive, what changed, where the user is, and what will happen next.
   - Tap, selected, disabled, saving, success, error, and recovery feedback must be immediate and unambiguous.
 4. Strong primary and secondary hierarchy
   - Every state has one P0 action or message, supporting P1 actions, and quiet P2 context.
   - Decorative ideas and secondary metrics must never compete with the current P0 task.
 5. Comfortable purpose-fit design
   - The interface should support calm focus, trust, repeat use, and low cognitive load rather than chase a fashionable genre.
   - Colors need semantic, emotional, accessibility, light/dark, and localization rationale.
   - Each route still needs one memorable product-specific visual or interaction idea; comfort is not permission to become generic.
 ### Supporting Rules
 1. Coherence without genre constraints
   - Clay, cyberpunk, glass, paper, floating surfaces, editorial layouts, and other labels are exploration vocabulary, not requirements or exclusions.
   - Derive the visual language from the product's calm focus loop, information hierarchy, interaction needs, audience, accessibility, localization, and performance constraints.