Material Design

# Material Design## 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 **Material Design** design language. Google 推动的跨平台设计系统，用纸张隐喻、明确 elevation、组件规范和 motion 规则建立可预测体验。Treat predictability, native conventions, accessibility, and component consistency as the main design material.## Aliases- Google Material## Category- 平台与系统## Target Platforms- 移动端- PC 端## SummaryGoogle 推动的跨平台设计系统，用纸张隐喻、明确 elevation、组件规范和 motion 规则建立可预测体验。## Visual DNA- elevation- 组件规范- 状态反馈- 栅格系统## Best Use Cases- Android 应用- 跨平台工具- 企业组件库- 表单流程## Avoid When品牌需要强烈差异化，或界面不希望带有明显 Google 系统气质。## Anatomy每个面板都有 elevation；按钮、输入框、导航和状态都遵循固定组件语义。## 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** `#f3f4f6`- **reference-3** `#6750a4`- **reference-4** `#eaddff`- **reference-5** `#1d1b20`### Seed Tokens- **colorBgBase** `#ffffff` - 页面基础背景.- **colorBgContainer** `#f7f7f7` - 卡片、面板与容器.- **colorFillSecondary** `#ededed` - 次级填充与弱状态.- **colorPrimary** `#eaddff` - 品牌主操作与选中态.- **colorTextBase** `#1d1b20` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#fdfcff`- **primary-2** `#faf8ff`- **primary-3** `#f7f3ff`- **primary-4** `#f4edff`- **primary-5** `#f0e7ff`- **primary-6** `#eaddff`- **primary-7** `#d1c6e4`- **primary-8** `#b9aec9`- **primary-9** `#a097af`- **primary-10** `#847c90`### Neutral Scale- **neutral-1** `#ffffff`- **neutral-2** `#f6f6f6`- **neutral-3** `#ededed`- **neutral-4** `#dbdbdb`- **neutral-5** `#c0bfc1`- **neutral-6** `#a09fa1`- **neutral-7** `#7c7b7e`- **neutral-8** `#5c5b5e`- **neutral-9** `#3d3b3f`- **neutral-10** `#1d1b20`### Semantic Tokens- **colorSuccess** `#16a34a` - 成功、在线、已完成.- **colorSuccessBg** `#e3f4e9` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#faefe1` - 警告状态浅背景.- **colorError** `#dc2626` - 错误、危险、阻断.- **colorErrorBg** `#fce9e9` - 错误状态浅背景.- **colorInfo** `#eaddff` - 信息、链接、进行中.- **colorInfoBg** `#fcfbff` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#fbfbfb` - 应用整体画布.- **colorBgElevated** `#f8f8f8` - 弹层、浮层与菜单.- **colorBgSpotlight** `#3d3b3f` - Tooltip 与强提示.- **colorBorder** `#dbdbdb` - 控件与容器边框.- **colorBorderSecondary** `#ededed` - 轻分隔线.- **colorText** `#1d1b20` - 一级文本.- **colorTextSecondary** `#656467` - 二级文本.- **colorTextTertiary** `#8e8d90` - 辅助说明.- **colorTextDisabled** `#b2b1b3` - 禁用文本.- **colorPrimaryHover** `#f0e7ff` - 主操作 Hover.- **colorPrimaryActive** `#d1c6e4` - 主操作 Active.- **colorPrimaryBorder** `#f4edff` - 主色边框.- **colorPrimaryBg** `#fdfcff` - 主色浅背景.- **colorLink** `#eaddff` - 链接与可跳转文本.- **colorFocus** `#f4edff` - 键盘焦点环.- **colorMask** `#151317` - 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 elevation, 组件规范, 状态反馈 without relying on a single color or effect.## Quality Checklist- The screen is immediately recognizable as **Material Design**, 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: 品牌需要强烈差异化，或界面不希望带有明显 Google 系统气质。## 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- material- google- elevation- components## Agent Prompt SnippetImplement the UI in the **Material Design** design language. Prioritize elevation, 组件规范, 状态反馈. 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 Android 应用, 跨平台工具, 企业组件库, while avoiding: 品牌需要强烈差异化，或界面不希望带有明显 Google 系统气质。