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 Reference only the product-specific principles from `docs/product/design-principles.md` that can change the current design decision. 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 requires every user-facing interaction to record Loading, Empty, Error, Partial, and Success as `required` or `not_applicable` with a reason. In practice: - PRDs specify behavior for every required state and preserve explicit reasons for states that do not apply - Prototypes implement the states needed to test the hypothesis and report the disposition of all five 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 f