Mobile Commerce

# Mobile Commerce## UsageUse this DESIGN.md as a reusable design brief for an AI coding agent. Apply it when building a new page, restyling an existing interface, or keeping multiple screens visually consistent.## Design IntentYou are implementing an interface using the **Mobile Commerce** design language. 围绕商品图、价格、优惠、购物车和下单路径优化移动端转化效率。Treat information architecture, scan paths, and component grouping as the main design material.## Aliases- 移动电商- shop app UI## Category- 布局与信息组织## Target Platforms- 移动端## Summary围绕商品图、价格、优惠、购物车和下单路径优化移动端转化效率。## Visual DNA- 商品卡片- 底部购买栏- 价格突出- 优惠标签## Best Use Cases- 电商 App- 小程序商城- 直播带货页- 品牌零售## Avoid When产品不是交易导向，或需要复杂配置和长周期决策。## Anatomy图片和价格优先；购买按钮固定在拇指热区；优惠信息必须清楚但不过载。## Color SystemUse a Seed → Map → Semantic → Alias token architecture. Components must consume named tokens instead of hard-coded colors.### Reference Palette- **reference-1** `#ffffff`- **reference-2** `#fff7ed`- **reference-3** `#ef4444`- **reference-4** `#f97316`- **reference-5** `#111827`### Seed Tokens- **colorBgBase** `#ffffff` - 页面基础背景.- **colorBgContainer** `#f7f7f7` - 卡片、面板与容器.- **colorFillSecondary** `#ecedee` - 次级填充与弱状态.- **colorPrimary** `#f97316` - 品牌主操作与选中态.- **colorTextBase** `#111827` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#fef1e8`- **primary-2** `#fee0cc`- **primary-3** `#fdcdab`- **primary-4** `#fcb686`- **primary-5** `#fb9a57`- **primary-6** `#f97316`- **primary-7** `#dd6818`- **primary-8** `#c15d1a`- **primary-9** `#a5521c`- **primary-10** `#85461f`### Neutral Scale- **neutral-1** `#ffffff`- **neutral-2** `#f5f6f6`- **neutral-3** `#ecedee`- **neutral-4** `#d9dadc`- **neutral-5** `#bcbec3`- **neutral-6** `#9b9ea4`- **neutral-7** `#757982`- **neutral-8** `#545963`- **neutral-9** `#323845`- **neutral-10** `#111827`### Semantic Tokens- **colorSuccess** `#16a34a` - 成功、在线、已完成.- **colorSuccessBg** `#e3f4e9` - 成功状态浅背景.- **colorWarning** `#f97316` - 警告、待确认、需关注.- **colorWarningBg** `#feeee3` - 警告状态浅背景.- **colorError** `#ef4444` - 错误、危险、阻断.- **colorErrorBg** `#fdecec` - 错误状态浅背景.- **colorInfo** `#f97316` - 信息、链接、进行中.- **colorInfoBg** `#feeee3` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#fafbfb` - 应用整体画布.- **colorBgElevated** `#f8f8f8` - 弹层、浮层与菜单.- **colorBgSpotlight** `#323845` - Tooltip 与强提示.- **colorBorder** `#d9dadc` - 控件与容器边框.- **colorBorderSecondary** `#ecedee` - 轻分隔线.- **colorText** `#111827` - 一级文本.- **colorTextSecondary** `#5d626c` - 二级文本.- **colorTextTertiary** `#888c93` - 辅助说明.- **colorTextDisabled** `#aeb0b6` - 禁用文本.- **colorPrimaryHover** `#fb9a57` - 主操作 Hover.- **colorPrimaryActive** `#dd6818` - 主操作 Active.- **colorPrimaryBorder** `#fcb686` - 主色边框.- **colorPrimaryBg** `#fef1e8` - 主色浅背景.- **colorLink** `#f97316` - 链接与可跳转文本.- **colorFocus** `#fcb686` - 键盘焦点环.- **colorMask** `#0c111c` - Modal 遮罩基础色.Color rules:- Use the palette as design tokens, not random decorative swatches.- Keep primary text and primary actions at accessible contrast.- Use primary-1 through primary-10 for interaction states instead of inventing new brand colors.- Use semantic tokens consistently for success, warning, error, and info; pair color with iconography or text.- Map component styles to Alias Tokens so theme changes do not require component-level color edits.## Typography- Use a modern system sans-serif stack by default; only introduce a custom font when the brand direction requires it.- Headings should be confident but not ornamental; body text must remain readable across mobile and desktop.- Keep labels short, high-contrast, and aligned to the component structure.## Layout And Spacing- Use an 8px spacing base; reserve 4px for micro-gaps and 32px+ for major layout separation.- Keep cards, panels, controls, and lists dimensionally stable across responsive breakpoints.- On mobile, reduce column count before reducing legibility.- Recommended radius: 8-16px radius for cards and controls; keep system consistency more important than novelty.- Elevation and shadow: Use shadows to separate interactive or elevated surfaces only; avoid stacking many shadow styles.## Component Rules- Components should reinforce the primary information structure rather than introduce a separate decorative style.- Primary actions must be visually obvious and reachable; secondary actions should be quieter but still discoverable.- Cards need a clear title, supporting text or metric, state, and one obvious next action when action is expected.- Forms and filters should use familiar controls, stable dimensions, clear labels, and visible focus states.- Empty, loading, error, and success states must use the same visual language, not generic placeholders.## Interaction And Motion- Use subtle 120-220ms transitions for hover, focus, open, close, and selection states.- Motion should clarify state changes rather than decorate the page.- Respect reduced-motion preferences.## Implementation Recipe1. Start with the real user workflow and page structure; do not make a generic landing page unless explicitly requested.2. Establish layout zones first: navigation, content, controls, feedback, and primary action.3. Apply the color tokens to semantic roles: canvas, surface, text, border, accent, danger, and success.4. Build reusable components that express this style: buttons, cards, inputs, tabs, filters, modals, empty states, and status badges.5. Verify mobile and desktop breakpoints before adding decorative polish.6. Check that the final screen still communicates 商品卡片, 底部购买栏, 价格突出 without relying on a single color or effect.## Quality Checklist- The screen is immediately recognizable as **Mobile Commerce**, not a generic Tailwind layout.- The design uses surface, spacing, typography, and component shape together; it does not rely only on colors.- Primary actions and navigation are clear on both mobile and desktop.- Text is readable, controls are stable, and content does not overlap or shift unexpectedly.- Empty, loading, hover, focus, selected, disabled, success, and error states are styled in the same language.- The implementation avoids the known failure mode: 产品不是交易导向，或需要复杂配置和长周期决策。## Anti-Patterns- Do not paste this palette onto an unrelated layout and call it finished.- Do not overuse decorative effects where the user needs to read, compare, or act quickly.- Do not mix this style with unrelated visual languages unless the product explicitly requires a hybrid.- Do not hide important state behind low contrast, blur, tiny text, or animation.## Keywords- mobile commerce- shop- ecommerce- checkout- mobile## Agent Prompt SnippetImplement the UI in the **Mobile Commerce** design language. Prioritize 商品卡片, 底部购买栏, 价格突出. Use the color roles, typography guidance, spacing rules, component rules, and anti-patterns from this DESIGN.md as hard constraints. The result should feel purpose-built for 电商 App, 小程序商城, 直播带货页, while avoiding: 产品不是交易导向，或需要复杂配置和长周期决策。