AI Command Center

# AI Command Center## 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 **AI Command Center** design language. 把对话、任务队列、执行日志、工具状态和结果预览放在同一个高密度工作台里，适合 Agent 和 AI Infra 产品。Treat information architecture, scan paths, and component grouping as the main design material.## Aliases- AI 指挥中心- agent console## Category- 布局与信息组织## Target Platforms- PC 端## Summary把对话、任务队列、执行日志、工具状态和结果预览放在同一个高密度工作台里，适合 Agent 和 AI Infra 产品。## Visual DNA- 多面板- 任务队列- 日志流- 状态监控## Best Use Cases- Agent 控制台- AI Infra- 自动化平台- 内部运营工具## 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** `#0f172a`- **reference-2** `#1e293b`- **reference-3** `#38bdf8`- **reference-4** `#a3e635`- **reference-5** `#f8fafc`### Seed Tokens- **colorBgBase** `#0f172a` - 页面基础背景.- **colorBgContainer** `#22293b` - 卡片、面板与容器.- **colorFillSecondary** `#32394a` - 次级填充与弱状态.- **colorPrimary** `#38bdf8` - 品牌主操作与选中态.- **colorTextBase** `#f8fafc` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#e5f4fc`- **primary-2** `#ceedfb`- **primary-3** `#b3e4fb`- **primary-4** `#94dafa`- **primary-5** `#6ecef9`- **primary-6** `#38bdf8`- **primary-7** `#33a9df`- **primary-8** `#2e95c7`- **primary-9** `#2981ae`- **primary-10** `#246a91`### 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** `#38bdf8` - 信息、链接、进行中.- **colorInfoBg** `#e1f3fc` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#171f32` - 应用整体画布.- **colorBgElevated** `#444a5a` - 弹层、浮层与菜单.- **colorBgSpotlight** `#303747` - Tooltip 与强提示.- **colorBorder** `#d3d6da` - 控件与容器边框.- **colorBorderSecondary** `#e5e8eb` - 轻分隔线.- **colorText** `#f8fafc` - 一级文本.- **colorTextSecondary** `#adb1b9` - 二级文本.- **colorTextTertiary** `#848993` - 辅助说明.- **colorTextDisabled** `#5e6471` - 禁用文本.- **colorPrimaryHover** `#6ecef9` - 主操作 Hover.- **colorPrimaryActive** `#33a9df` - 主操作 Active.- **colorPrimaryBorder** `#94dafa` - 主色边框.- **colorPrimaryBg** `#e5f4fc` - 主色浅背景.- **colorLink** `#38bdf8` - 链接与可跳转文本.- **colorFocus** `#94dafa` - 键盘焦点环.- **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 **AI Command Center**, 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- ai- agent- command center- console- pc## Agent Prompt SnippetImplement the UI in the **AI Command Center** 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 Agent 控制台, AI Infra, 自动化平台, while avoiding: 用户只需要单轮对话或低频轻量查询。