Spring UX Variant

Use this skill only when UX judgment should influence the design beyond direct implementation of an approved design file.

When To Use

• Designing a new target-user variant.
• Vibe-coding a screen without a complete Figma design.
• Refining copy, tone, trust, urgency, or financial anxiety.
• Reducing drop-off or clarifying a stalled application moment.
• Designing or reviewing declined, success, verification, or reactivation states.
• Checking AppFlow step order, branches, progress labels, or outcomes.

When Not To Use

• A complete Figma design is provided and no UX variation is requested.
• The task is only component export, route wiring, token sync, or file cleanup.
• The task is a pure design-system implementation with no copy, flow, or behavior decision.

Source Order

1. Read docs/ux/user-insights-report.md when a target user, persona, or behavior is involved.
2. Read docs/ux/ux-strategy-logic.md when trust, urgency, copy, decline, success, or drop-off is involved.
3. Read docs/ux/personal-loans-flow.md only when AppFlow step order, branch logic, progress labels, or outcomes are affected.
4. Read docs/ai/workflow-contracts.md before proposing file placement or implementation.

Required Output

Before implementation, state:

• selected persona or "no persona variant needed"
• selected UX intent: Validation, Relief, Advisory, or Re-activation
• layout implication
• copy/tone implication
• whether AppFlow structure is affected
• whether the change deviates from the supplied design and needs user approval

Guardrails

• Do not override a completed approved design unless the user asks for UX refinement or a variant.
• Do not use persona guidance as a substitute for AppFlow step order; use personal-loans-flow.md for flow logic.
• Keep gallery/AppFlow screens presentational and free of production APIs, analytics, database access, and partner integrations.