AI UI Atlas
Mapping interface systems
给 coding agent 时可以直接复制下面这段,作为 UI 风格约束。
# Acrylic UI## 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 **Acrylic UI** design language. 用半透明、噪点纹理、背景染色和边缘高光形成类似 Windows Fluent 的亚克力表面,适合桌面级浮层和侧栏。Treat surface, depth, light, and texture as the main carrier of brand expression.## Aliases- 亚克力材质- fluent acrylic## Category- 材质与表面## Target Platforms- PC 端## Summary用半透明、噪点纹理、背景染色和边缘高光形成类似 Windows Fluent 的亚克力表面,适合桌面级浮层和侧栏。## Visual DNA- 半透明染色- 细噪点- 背景模糊- 边缘高光## Best Use Cases- 桌面应用- 侧边导航- 系统浮层- 媒体工具## Avoid When移动低端设备、背景不可控、文本密集或需要强对比阅读的页面。## Anatomy亚克力需要 tint、blur、noise 和 border 四层配合;正文区域要提高不透明度,避免阅读漂浮。## Color SystemUse a Seed → Map → Semantic → Alias token architecture. Components must consume named tokens instead of hard-coded colors.### Reference Palette- **reference-1** `#f8fafc`- **reference-2** `#dbeafe`- **reference-3** `#93c5fd`- **reference-4** `#64748b`- **reference-5** `#0f172a`### Seed Tokens- **colorBgBase** `#f8fafc` - 页面基础背景.- **colorBgContainer** `#f0f2f5` - 卡片、面板与容器.- **colorFillSecondary** `#e5e8eb` - 次级填充与弱状态.- **colorPrimary** `#93c5fd` - 品牌主操作与选中态.- **colorTextBase** `#0f172a` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#eef5fc`- **primary-2** `#e2eefc`- **primary-3** `#d4e7fc`- **primary-4** `#c3defd`- **primary-5** `#afd4fd`- **primary-6** `#93c5fd`- **primary-7** `#83b0e4`- **primary-8** `#739bca`- **primary-9** `#6386b1`- **primary-10** `#516e94`### Neutral Scale- **neutral-1** `#f8fafc`- **neutral-2** `#eff1f4`- **neutral-3** `#e5e8eb`- **neutral-4** `#d3d6da`- **neutral-5** `#b7bac1`- **neutral-6** `#969ba4`- **neutral-7** `#717682`- **neutral-8** `#505765`- **neutral-9** `#303747`- **neutral-10** `#0f172a`### Semantic Tokens- **colorSuccess** `#16a34a` - 成功、在线、已完成.- **colorSuccessBg** `#ddf0e7` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#f4eade` - 警告状态浅背景.- **colorError** `#dc2626` - 错误、危险、阻断.- **colorErrorBg** `#f5e5e7` - 错误状态浅背景.- **colorInfo** `#93c5fd` - 信息、链接、进行中.- **colorInfoBg** `#ecf4fc` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#f3f6f8` - 应用整体画布.- **colorBgElevated** `#f1f3f6` - 弹层、浮层与菜单.- **colorBgSpotlight** `#303747` - Tooltip 与强提示.- **colorBorder** `#d3d6da` - 控件与容器边框.- **colorBorderSecondary** `#e5e8eb` - 轻分隔线.- **colorText** `#0f172a` - 一级文本.- **colorTextSecondary** `#5a606d` - 二级文本.- **colorTextTertiary** `#848993` - 辅助说明.- **colorTextDisabled** `#a9adb5` - 禁用文本.- **colorPrimaryHover** `#afd4fd` - 主操作 Hover.- **colorPrimaryActive** `#83b0e4` - 主操作 Active.- **colorPrimaryBorder** `#c3defd` - 主色边框.- **colorPrimaryBg** `#eef5fc` - 主色浅背景.- **colorLink** `#93c5fd` - 链接与可跳转文本.- **colorFocus** `#c3defd` - 键盘焦点环.- **colorMask** `#0b111e` - 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: 16-32px radius for major surfaces; use pill shapes only where they improve touch targets or softness.- Elevation and shadow: Use environment-tinted outer shadows and backdrop blur for elevation. Avoid closed white perimeter borders and full inset highlights that make glass look plastic; add a low-contrast same-color edge only when adjacent layers cannot separate. Contrast must come from text and component state, not blur alone.## Component Rules- Components should make the surface logic visible: panels, buttons, inputs, and overlays need consistent material treatment.- 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 slow, soft transitions for surface changes, highlights, and overlays.- Avoid constant background motion behind readable text.- Respect reduced-motion preferences and provide a static equivalent.## 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 **Acrylic UI**, 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- acrylic- fluent- blur- desktop- surface## Agent Prompt SnippetImplement the UI in the **Acrylic UI** 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: 移动低端设备、背景不可控、文本密集或需要强对比阅读的页面。