Verify FWF UI
Produce evidence, not aesthetic vibes.
Workflow
- Read repo
docs/skills/fartwithfriends-ui/SKILL.mdand the owning source/tests. - Identify the screen job, hero, novel verb, privacy/consent boundary, and state matrix.
- Run the smallest relevant Flutter analyze/test set, then broaden only if shared contracts changed.
- Review visual tokens, semantics, text scaling, hit targets, reduced motion/transparency, and cancellation paths.
- Report failures by contract and file/line; distinguish source proof from device-only evidence.
Mandatory Checks
- Shell labels/order and 80px logo-based center action.
- All public vs Friends' public map filtering; no private data path.
- Hold playback and reaction recording start/stop together after consent.
- Preview-before-send and re-record/discard paths.
- Default, pressed, focus, disabled, loading, and error for changed controls.
- Empty, partial, long, offline, and permission-denied screen states.
- 44–48dp targets, semantic labels, logical focus order, and large-text survival.
- One authored route silhouette, no universal card borders, no random accent-per-item, and no continuous decorative atmosphere.
References
references/profiles.md— targeted validation profiles and evidence boundaries.