Form-Heavy Enterprise

# Form-Heavy Enterprise## 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 **Form-Heavy Enterprise** design language. 以表单、校验、步骤、审批和数据录入为核心，强调稳定、可恢复和低错误率。Treat information architecture, scan paths, and component grouping as the main design material.## Aliases- 重表单企业 UI- enterprise forms## Category- 布局与信息组织## Target Platforms- PC 端## Summary以表单、校验、步骤、审批和数据录入为核心，强调稳定、可恢复和低错误率。## Visual DNA- 分组表单- 步骤条- 校验反馈- 审批状态## Best Use Cases- ERP- 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** `#ffffff`- **reference-2** `#f8fafc`- **reference-3** `#dbeafe`- **reference-4** `#2563eb`- **reference-5** `#b91c1c`### Seed Tokens- **colorBgBase** `#ffffff` - 页面基础背景.- **colorBgContainer** `#fdf7f7` - 卡片、面板与容器.- **colorFillSecondary** `#f9eded` - 次级填充与弱状态.- **colorPrimary** `#dbeafe` - 品牌主操作与选中态.- **colorTextBase** `#b91c1c` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#fbfdff`- **primary-2** `#f7faff`- **primary-3** `#f2f7ff`- **primary-4** `#ecf4fe`- **primary-5** `#e5f0fe`- **primary-6** `#dbeafe`- **primary-7** `#d7d1e3`- **primary-8** `#d3b9c8`- **primary-9** `#cfa0ad`- **primary-10** `#ca838d`### Neutral Scale- **neutral-1** `#ffffff`- **neutral-2** `#fcf6f6`- **neutral-3** `#f9eded`- **neutral-4** `#f4dbdb`- **neutral-5** `#ebbfbf`- **neutral-6** `#e2a0a0`- **neutral-7** `#d67b7b`- **neutral-8** `#cd5c5c`- **neutral-9** `#c33c3c`- **neutral-10** `#b91c1c`### Semantic Tokens- **colorSuccess** `#16a34a` - 成功、在线、已完成.- **colorSuccessBg** `#e3f4e9` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#faefe1` - 警告状态浅背景.- **colorError** `#b91c1c` - 错误、危险、阻断.- **colorErrorBg** `#f8e8e8` - 错误状态浅背景.- **colorInfo** `#2563eb` - 信息、链接、进行中.- **colorInfoBg** `#e5ecfd` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#fefbfb` - 应用整体画布.- **colorBgElevated** `#fdf8f8` - 弹层、浮层与菜单.- **colorBgSpotlight** `#c33c3c` - Tooltip 与强提示.- **colorBorder** `#f4dbdb` - 控件与容器边框.- **colorBorderSecondary** `#f9eded` - 轻分隔线.- **colorText** `#b91c1c` - 一级文本.- **colorTextSecondary** `#cf6565` - 二级文本.- **colorTextTertiary** `#dc8e8e` - 辅助说明.- **colorTextDisabled** `#e7b2b2` - 禁用文本.- **colorPrimaryHover** `#e5f0fe` - 主操作 Hover.- **colorPrimaryActive** `#d7d1e3` - 主操作 Active.- **colorPrimaryBorder** `#ecf4fe` - 主色边框.- **colorPrimaryBg** `#fbfdff` - 主色浅背景.- **colorLink** `#dbeafe` - 链接与可跳转文本.- **colorFocus** `#ecf4fe` - 键盘焦点环.- **colorMask** `#851414` - 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 **Form-Heavy Enterprise**, 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- enterprise- form- workflow- pc- admin## Agent Prompt SnippetImplement the UI in the **Form-Heavy Enterprise** 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 ERP, CRM, 审批系统, while avoiding: 营销页面、轻互动产品或视觉表达优先的场景。