---
name: web-ui-builder
description: Build or refine web-lane interfaces for landing, waitlist, trust, and later content. Use when implementing website UI that must stay faithful to product truth while remaining separate from mobile UX assumptions.
---

# Web UI Builder

1. Read `docs/product/web/website-prd.md`, `docs/product/web/landing-page-strategy.md`, `docs/architecture/web/web-architecture.md`, and `docs/agent-workflows/ui-design-standard.md`.
2. Keep web concerns separate from the mobile product lane.
3. Ground messaging in real differentiators: Safe-to-Spend, admin work elimination, forward-looking cash flow, reimbursement correctness, and privacy-first trust.
4. Share schemas and contracts through packages without prematurely sharing UI.
5. External tools such as Stitch, Gemini image generation, 21st.dev, or similar systems may inform ideation, but they are not the source of truth. Keep sensitive data out of them and record material reference provenance in the active spec or review notes.
6. Use visual verification for web UI changes when possible, and explicitly check responsive behavior, loading and error states, contrast, and reduced-motion friendliness.
7. Update docs when structure or messaging changes materially.