Wizard Flow

# Wizard Flow## 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 **Wizard Flow** design language. 把复杂任务拆成连续步骤，降低单屏压力，适合配置、注册、部署和购买流程。Treat information architecture, scan paths, and component grouping as the main design material.## Aliases- 向导式流程- stepper UI## Category- 布局与信息组织## Target Platforms- 移动端- PC 端## Summary把复杂任务拆成连续步骤，降低单屏压力，适合配置、注册、部署和购买流程。## Visual DNA- 步骤条- 单步聚焦- 进度反馈- 明确返回## Best Use Cases- 注册流程- 部署配置- 购买结算- 导入向导## 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** `#f1f5f9`- **reference-3** `#2563eb`- **reference-4** `#22c55e`- **reference-5** `#111827`### Seed Tokens- **colorBgBase** `#ffffff` - 页面基础背景.- **colorBgContainer** `#f7f7f7` - 卡片、面板与容器.- **colorFillSecondary** `#ecedee` - 次级填充与弱状态.- **colorPrimary** `#2563eb` - 品牌主操作与选中态.- **colorTextBase** `#111827` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#e9effd`- **primary-2** `#cfddfb`- **primary-3** `#b1c7f8`- **primary-4** `#8eaef5`- **primary-5** `#628ff1`- **primary-6** `#2563eb`- **primary-7** `#235ad3`- **primary-8** `#2051bc`- **primary-9** `#1e48a4`- **primary-10** `#1b3e89`### 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** `#22c55e` - 成功、在线、已完成.- **colorSuccessBg** `#e4f8ec` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#faefe1` - 警告状态浅背景.- **colorError** `#dc2626` - 错误、危险、阻断.- **colorErrorBg** `#fce9e9` - 错误状态浅背景.- **colorInfo** `#2563eb` - 信息、链接、进行中.- **colorInfoBg** `#e5ecfd` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#fafbfb` - 应用整体画布.- **colorBgElevated** `#f8f8f8` - 弹层、浮层与菜单.- **colorBgSpotlight** `#323845` - Tooltip 与强提示.- **colorBorder** `#d9dadc` - 控件与容器边框.- **colorBorderSecondary** `#ecedee` - 轻分隔线.- **colorText** `#111827` - 一级文本.- **colorTextSecondary** `#5d626c` - 二级文本.- **colorTextTertiary** `#888c93` - 辅助说明.- **colorTextDisabled** `#aeb0b6` - 禁用文本.- **colorPrimaryHover** `#628ff1` - 主操作 Hover.- **colorPrimaryActive** `#235ad3` - 主操作 Active.- **colorPrimaryBorder** `#8eaef5` - 主色边框.- **colorPrimaryBg** `#e9effd` - 主色浅背景.- **colorLink** `#2563eb` - 链接与可跳转文本.- **colorFocus** `#8eaef5` - 键盘焦点环.- **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 **Wizard Flow**, 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- wizard- stepper- flow- onboarding- mobile- pc## Agent Prompt SnippetImplement the UI in the **Wizard Flow** 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 注册流程, 部署配置, 购买结算, while avoiding: 任务很简单，或用户需要同时查看所有字段做全局判断。