Retro Operational Dashboard

# Retro 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 **Retro Operational Dashboard** design language. 把 Retro 终端/像素气质和 Operational Dashboard 的高密度监控结构结合起来，适合开发者工具、运维监控、复古主题数据产品。Treat cultural references, period details, and restraint as the main design material.## Aliases- 复古运营后台- terminal dashboard- retro ops## Category- 复古与文化风格## Target Platforms- 移动端- PC 端## Summary把 Retro 终端/像素气质和 Operational Dashboard 的高密度监控结构结合起来，适合开发者工具、运维监控、复古主题数据产品。## 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** `#0b1020`- **reference-2** `#22c55e`- **reference-3** `#facc15`- **reference-4** `#38bdf8`- **reference-5** `#e5e7eb`### Seed Tokens- **colorBgBase** `#0b1020` - 页面基础背景.- **colorBgContainer** `#1c2130` - 卡片、面板与容器.- **colorFillSecondary** `#2c303e` - 次级填充与弱状态.- **colorPrimary** `#38bdf8` - 品牌主操作与选中态.- **colorTextBase** `#e5e7eb` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#d4e3ec`- **primary-2** `#bfdeee`- **primary-3** `#a7d8f0`- **primary-4** `#8bd1f2`- **primary-5** `#68c9f4`- **primary-6** `#38bdf8`- **primary-7** `#33a8de`- **primary-8** `#2d93c4`- **primary-9** `#287faa`- **primary-10** `#22678c`### Neutral Scale- **neutral-1** `#e5e7eb`- **neutral-2** `#dcdee3`- **neutral-3** `#d4d6db`- **neutral-4** `#c2c5cb`- **neutral-5** `#a8abb2`- **neutral-6** `#898d96`- **neutral-7** `#676a75`- **neutral-8** `#484c59`- **neutral-9** `#2a2e3c`- **neutral-10** `#0b1020`### Semantic Tokens- **colorSuccess** `#22c55e` - 成功、在线、已完成.- **colorSuccessBg** `#cee3da` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#e4dad0` - 警告状态浅背景.- **colorError** `#dc2626` - 错误、危险、阻断.- **colorErrorBg** `#e4d4d7` - 错误状态浅背景.- **colorInfo** `#38bdf8` - 信息、链接、进行中.- **colorInfoBg** `#d0e2ed` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#131827` - 应用整体画布.- **colorBgElevated** `#3c414e` - 弹层、浮层与菜单.- **colorBgSpotlight** `#2a2e3c` - Tooltip 与强提示.- **colorBorder** `#c2c5cb` - 控件与容器边框.- **colorBorderSecondary** `#d4d6db` - 轻分隔线.- **colorText** `#e5e7eb` - 一级文本.- **colorTextSecondary** `#9fa2aa` - 二级文本.- **colorTextTertiary** `#787c86` - 辅助说明.- **colorTextDisabled** `#555965` - 禁用文本.- **colorPrimaryHover** `#68c9f4` - 主操作 Hover.- **colorPrimaryActive** `#33a8de` - 主操作 Active.- **colorPrimaryBorder** `#8bd1f2` - 主色边框.- **colorPrimaryBg** `#d4e3ec` - 主色浅背景.- **colorLink** `#38bdf8` - 链接与可跳转文本.- **colorFocus** `#8bd1f2` - 键盘焦点环.- **colorMask** `#080c17` - 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: 0-6px radius; favor crisp edges and deliberate geometry.- 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 **Retro 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- retro dashboard- terminal- ops- monitoring- developer tool## Agent Prompt SnippetImplement the UI in the **Retro 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 开发者工具, 运维监控, 日志分析, while avoiding: 大众消费产品、移动端长阅读、需要现代品牌高级感的页面。