juspay Design brief
Translate the request into an implementation brief without asking for approval unless a genuinely blocking choice is missing.
- Identify the primary user, their immediate goal, and the single most important action on the screen.
- Extract required content and states: default, empty, loading, error, success, disabled, and destructive confirmation where relevant.
- Choose a clear page hierarchy. Each region must earn its space; avoid a dashboard grid when a focused flow would work better.
- Record constraints from the user or existing artifact. Preserve established brand language and useful structure during revisions.
- Define observable acceptance checks for layout, interaction, responsiveness, accessibility, and delivery.
Prefer specific product copy over placeholder prose. Do not invent metrics, customer quotes, legal claims, or functionality the brief did not request.