Operational Dashboard

# Operational Dashboard## 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 **Operational Dashboard** design language. 面向高频操作和数据监控，追求密度、可扫描、稳定布局和明确状态，而不是视觉惊艳。Treat information architecture, scan paths, and component grouping as the main design material.## Aliases- 运营后台风格- dense enterprise UI## Category- 布局与信息组织## Target Platforms- 移动端- PC 端## Summary面向高频操作和数据监控，追求密度、可扫描、稳定布局和明确状态，而不是视觉惊艳。## Visual DNA- 高信息密度- 表格优先- 状态标签- 固定工具栏## Best Use Cases- CRM- 风控后台- 投放平台- 运维控制台## 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** `#f8fafc`- **reference-2** `#ffffff`- **reference-3** `#dbeafe`- **reference-4** `#2563eb`- **reference-5** `#0f172a`### Seed Tokens- **colorBgBase** `#f8fafc` - 页面基础背景.- **colorBgContainer** `#f0f2f5` - 卡片、面板与容器.- **colorFillSecondary** `#e5e8eb` - 次级填充与弱状态.- **colorPrimary** `#dbeafe` - 品牌主操作与选中态.- **colorTextBase** `#0f172a` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#fbfdff`- **primary-2** `#f7faff`- **primary-3** `#f2f7ff`- **primary-4** `#ecf4fe`- **primary-5** `#e5f0fe`- **primary-6** `#dbeafe`- **primary-7** `#c3d1e5`- **primary-8** `#aab7cb`- **primary-9** `#929eb2`- **primary-10** `#758194`### Neutral Scale- **neutral-1** `#ffffff`- **neutral-2** `#f5f6f6`- **neutral-3** `#ececee`- **neutral-4** `#d9dadd`- **neutral-5** `#bcbec3`- **neutral-6** `#9a9ea6`- **neutral-7** `#747883`- **neutral-8** `#525866`- **neutral-9** `#313748`- **neutral-10** `#0f172a`### Semantic Tokens- **colorSuccess** `#16a34a` - 成功、在线、已完成.- **colorSuccessBg** `#e3f4e9` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#faefe1` - 警告状态浅背景.- **colorError** `#dc2626` - 错误、危险、阻断.- **colorErrorBg** `#fce9e9` - 错误状态浅背景.- **colorInfo** `#2563eb` - 信息、链接、进行中.- **colorInfoBg** `#e5ecfd` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#f3f6f8` - 应用整体画布.- **colorBgElevated** `#f2f4f7` - 弹层、浮层与菜单.- **colorBgSpotlight** `#313748` - Tooltip 与强提示.- **colorBorder** `#d9dadd` - 控件与容器边框.- **colorBorderSecondary** `#ececee` - 轻分隔线.- **colorText** `#0f172a` - 一级文本.- **colorTextSecondary** `#5a606d` - 二级文本.- **colorTextTertiary** `#848993` - 辅助说明.- **colorTextDisabled** `#a9adb5` - 禁用文本.- **colorPrimaryHover** `#e5f0fe` - 主操作 Hover.- **colorPrimaryActive** `#c3d1e5` - 主操作 Active.- **colorPrimaryBorder** `#ecf4fe` - 主色边框.- **colorPrimaryBg** `#fbfdff` - 主色浅背景.- **colorLink** `#dbeafe` - 链接与可跳转文本.- **colorFocus** `#ecf4fe` - 键盘焦点环.- **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 precise sans-serif for UI labels and optionally a monospace accent for metrics, logs, or technical values.- Keep labels compact and scannable; prioritize numeric alignment and status readability.- Avoid decorative type in dense operational areas.## Layout And Spacing- Use compact but breathable spacing: 8px base unit, 12-16px card padding, 20-24px section gaps.- Desktop layouts should favor stable sidebars, tables, cards, and control strips over decorative hero sections.- Mobile layouts should collapse into one column with filters and controls above results.- Recommended radius: 6-12px radius by default; increase only for expressive or highly tactile components.- 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 **Operational Dashboard**, 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- dashboard- enterprise- table- dense## Agent Prompt SnippetImplement the UI in the **Operational Dashboard** 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 CRM, 风控后台, 投放平台, while avoiding: 品牌官网、活动页、需要情绪感染的内容页面。