Archive the differentiated YuXinGu product docs, AI engineering system, design contract, and Go/Vue scaffold. Next execution prioritizes Cece-parity over early innovation (see .ai/product/STRATEGY.md). Co-authored-by: Cursor <cursoragent@cursor.com>
1.0 KiB
1.0 KiB
Platform Contract — Flutter / Native App
Future client. Not in MVP scope unless task explicitly opens it.
Design language: ../design-system.md · Catalog names stay the same.
Priority
Performance > Native experience > Visual decoration
MUST
- Map tokens to
ThemeData/ design token classes — same hex and spacing scale. - Native navigation patterns (Material/Cupertino as decided by ADR).
- Platform permissions (camera, photos, notifications) only with clear UX rationale.
- 60fps interactions; avoid heavy blur/shadow on low-end devices.
- Reuse catalog component names (
Button,ChatBubble,SubscriptionCard…). - Same compliance and domain copy rules.
MUST NOT
- Invent a dark-neon “AI app” skin.
- Bypass API unlock/membership rules with local flags.
- Port Web DOM assumptions.
Checklist
- Token theme 1:1 with
packages/ui - Catalog parity for screens in scope
- Permission + performance considered
- ADR if introducing Flutter stack officially