72 lines
3.0 KiB
Markdown
72 lines
3.0 KiB
Markdown
# Design System Inspired by Ant
|
||
|
||
> Category: Professional & Corporate
|
||
> Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.
|
||
|
||
## 1. Visual Theme & Atmosphere
|
||
|
||
Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.
|
||
|
||
- **Visual style:** data-dense, enterprise
|
||
- **Color stance:** primary, neutral, success, warning, danger
|
||
- **Design intent:** Keep outputs recognizable to this style family while preserving usability and readability.
|
||
|
||
## 2. Color
|
||
|
||
- **Primary:** `#1677FF` — Token from style foundations.
|
||
- **Secondary:** `#8B5CF6` — Token from style foundations.
|
||
- **Success:** `#16A34A` — Token from style foundations.
|
||
- **Warning:** `#D97706` — Token from style foundations.
|
||
- **Danger:** `#DC2626` — Token from style foundations.
|
||
- **Surface:** `#FFFFFF` — Token from style foundations.
|
||
- **Text:** `#111827` — Token from style foundations.
|
||
- **Neutral:** `#FFFFFF` — Derived from the surface token for official format compatibility.
|
||
|
||
- Favor Primary (#1677FF) for CTA emphasis.
|
||
- Use Surface (#FFFFFF) for large backgrounds and cards.
|
||
- Keep body copy on Text (#111827) for legibility.
|
||
|
||
## 3. Typography
|
||
|
||
- **Scale:** 12/14/16/20/24/32
|
||
- **Families:** primary=Plus Jakarta Sans, display=Plus Jakarta Sans, mono=JetBrains Mono
|
||
- **Weights:** 100, 200, 300, 400, 500, 600, 700, 800, 900
|
||
- Headings should carry the style personality; body text should optimize scanability and contrast.
|
||
|
||
## 4. Spacing & Grid
|
||
|
||
- **Spacing scale:** 4/8/12/16/24/32
|
||
- Keep vertical rhythm consistent across sections and components.
|
||
- Align columns and modules to a predictable grid; avoid ad-hoc offsets.
|
||
|
||
## 5. Layout & Composition
|
||
|
||
- Prefer clear content blocks with consistent internal padding.
|
||
- Keep hierarchy obvious: headline → support text → primary action.
|
||
- Use whitespace to separate concerns before adding borders or shadows.
|
||
|
||
## 6. Components
|
||
|
||
- Buttons: primary action uses `#1677FF`; secondary actions stay neutral.
|
||
- Inputs: strong focus-visible states, clear labels, and predictable error messaging.
|
||
- Cards/sections: use consistent radii, spacing, and elevation strategy across the page.
|
||
|
||
## 7. Motion & Interaction
|
||
|
||
- Use subtle transitions that emphasize Primary (#1677FF) as the interaction signal.
|
||
- Default to short, purposeful transitions (150–250ms) with stable easing.
|
||
- Ensure hover, focus-visible, active, disabled, and loading states are explicit.
|
||
|
||
## 8. Voice & Brand
|
||
|
||
- Tone should reflect the visual style: concise, confident, and product-specific.
|
||
- Keep microcopy action-oriented and avoid generic filler language.
|
||
- Preserve the style identity in headlines while keeping UI labels literal and clear.
|
||
|
||
## 9. Anti-patterns
|
||
|
||
- Do not introduce off-palette colors when an existing token can solve the problem.
|
||
- Do not flatten hierarchy by using the same type size/weight for all text.
|
||
- Do not add decorative effects that reduce readability or accessibility.
|
||
- Do not mix unrelated visual metaphors in the same interface.
|