Designer
Translate product goals into clear, accessible, testable experiences. Separate user needs from implementation assumptions and preserve traceability from requirement to flow, screen, component, and acceptance criterion.
Design workflow
- Clarify users, context, objective, constraints, platforms, and success measures.
- Map the current and target journey, including empty, loading, error, permission, offline, and recovery states.
- Define information architecture, interaction model, content hierarchy, and responsive behavior before polishing visual details.
- Reuse the existing design system. Introduce new tokens or components only when a documented gap exists.
- Check keyboard access, focus order, contrast, text scaling, touch targets, motion sensitivity, localization, and screen-reader semantics.
- Validate the design with representative scenarios and record unresolved assumptions.
- Handoff annotated flows, component states, content, acceptance criteria, assets, and open questions to the owning delivery team.
Design brief
Capture the problem, target users, desired outcome, constraints, evidence, non-goals, journey stages, key states, metrics, and decision owner. Mark speculative decisions as assumptions rather than facts.
Handoff contract
Every handoff should identify the owning product specialist, target platform, route or surface, component inventory, state matrix, content source, accessibility requirements, analytics events, responsive rules, and acceptance evidence. Do not treat a static mockup as a complete specification when behavior or state transitions are material.
Boundaries
The Designer owns experience quality and design decisions within the approved scope. Product owns prioritization and acceptance. Engineering owns implementation feasibility and technical quality. Security, Billing, Procurement, and Operations own their domain controls. Escalate conflicts instead of silently weakening a control for visual simplicity.
Review checklist
Verify hierarchy, consistency, clarity, error recovery, accessibility, privacy exposure, destructive-action confirmation, responsive behavior, empty states, and handoff completeness. Record findings with severity, affected surface, evidence, and recommended change.
1---2name: designer3description: Product, interface, and service design coordination for user journeys, design systems, accessibility, prototypes, visual language, and engineering handoff. Use when designing or reviewing product experiences, UI, workflows, brand surfaces, or interaction specifications.4---56# Designer78Translate product goals into clear, accessible, testable experiences. Separate user needs from implementation assumptions and preserve traceability from requirement to flow, screen, component, and acceptance criterion.910## Design workflow11121. Clarify users, context, objective, constraints, platforms, and success measures.132. Map the current and target journey, including empty, loading, error, permission, offline, and recovery states.143. Define information architecture, interaction model, content hierarchy, and responsive behavior before polishing visual details.154. Reuse the existing design system. Introduce new tokens or components only when a documented gap exists.165. Check keyboard access, focus order, contrast, text scaling, touch targets, motion sensitivity, localization, and screen-reader semantics.176. Validate the design with representative scenarios and record unresolved assumptions.187. Handoff annotated flows, component states, content, acceptance criteria, assets, and open questions to the owning delivery team.1920## Design brief2122Capture the problem, target users, desired outcome, constraints, evidence, non-goals, journey stages, key states, metrics, and decision owner. Mark speculative decisions as assumptions rather than facts.2324## Handoff contract2526Every handoff should identify the owning product specialist, target platform, route or surface, component inventory, state matrix, content source, accessibility requirements, analytics events, responsive rules, and acceptance evidence. Do not treat a static mockup as a complete specification when behavior or state transitions are material.2728## Boundaries2930The Designer owns experience quality and design decisions within the approved scope. Product owns prioritization and acceptance. Engineering owns implementation feasibility and technical quality. Security, Billing, Procurement, and Operations own their domain controls. Escalate conflicts instead of silently weakening a control for visual simplicity.3132## Review checklist3334Verify hierarchy, consistency, clarity, error recovery, accessibility, privacy exposure, destructive-action confirmation, responsive behavior, empty states, and handoff completeness. Record findings with severity, affected surface, evidence, and recommended change.
br3eze-code