Trust and security communication patterns

[Baskarayelu]

Description

Short explainers for on-chain actions, USDC, and non-custodial assumptions where relevant.

Requirements and context

• Deliver Figma (or agreed design tool) frames with mobile, tablet, and desktop breakpoints.
• Target WCAG 2.1 AA for color contrast, focus visibility, and touch targets where applicable.
• Align visual language with existing Tailwind usage; call out new tokens if engineering must extend tailwind.config.js.
• Provide annotated handoff: spacing, type styles, component states, and interaction notes (hover, focus, disabled, loading, error).

Suggested execution

• Fork or branch the design file; map screens to Next.js routes under app/ for traceability.
• Audit current UI implementation and note gaps vs desired patterns.
• Produce high-fidelity mocks and a short component/state inventory for engineering.

Deliverables and handoff

• Figma link (or attached file) with named pages per feature area.
• Redlines or dev mode specs for critical screens.
• List of open questions for product/engineering (contract limits, copy, edge cases).

Example closure note

design: handoff approved — Figma link + eng sign-off

Guidelines

• Prefer evidence-based layout decisions (scan paths, primary tasks).
• Timeframe: 40–80 hours per major area unless noted narrower in comments.
• Run a quick design review with engineering before final sign-off.

[drips-wave]

Congratulations, @Jeyvers! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Jeyvers: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[BigMick03]

@BigMick03 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Good evening, please assign this to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @BigMick03 to this issue.

[drips-wave]

Congratulations, @BigMick03! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @BigMick03: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊