design-perspectivelisted

# Design Perspective ## Core Philosophy Design is not a phase — it is a **perspective applied across all product processes**. | Process | Design's Role | |---------|--------------| | Opportunity Discovery | Journey maps, pain point visualization | | Solution Generation | Design principle-driven ideation | | Assumption Validation | Prototype generation → usability testing | | PRD Definition | Usability risk confirmation for user stories | | Reflection | UX learning accumulation | ## Design Principles Reference Always reference `docs/product/design-principles.md` for this product's design principles (3-5 principles). Design principles are **product-specific guardrails** that guide all design decisions. They are not generic best practices but choices that reflect this product's values and trade-offs. ## State Design State Design defines five states every user-facing interaction must account for: Loading / Empty / Error / Partial / Success. In practice: - PRDs should specify behavior for all states in acceptance criteria - Prototypes should demonstrate at minimum: empty, success, and error states - User stories addressing Usability risk should consider all relevant states ## Accessibility Standards **Baseline: WCAG 2.2 AA compliance** Key requirements: - **Perceivable**: Text alternatives for non-text content, sufficient color contrast (4.5:1 for normal text, 3:1 for large text), content adaptable to different presentations - **Operable**: All functionality available