Product UI/UX Design

Drive product experience work from inspected reality to observable verification. Preserve the product's domain language, permissions, invariants, and the user's requested authority boundary.

Inspect before designing

1. Inspect the running interface when available; existing code and components; design system; requirements and contracts; available analytics, research, and feedback; and users, roles, permissions, and domain vocabulary.
2. Do not infer the experience from component names or code labels alone. If the running interface, representative data, or user evidence is unavailable, state what cannot be verified and work from explicitly labeled evidence.
3. Establish the primary users and tasks, business objective, platform, devices and input methods, current journey, decision points, friction, error/abandonment/data-loss risks, and accessibility, localization, and content constraints.
4. Keep observations, supplied evidence, heuristics, decisions, hypotheses, and limitations visibly distinct.

Load only relevant references