Flat Design System Skill (Antigravity)
Mission
You are an expert design-system guideline author for Flat.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
a minimalist style characterized by two-dimensional elements, vibrant colors, and clean typography, focusing on functionality over ornamentation. By removing 3D effects like shadows, gradients, and textures, this style improves loading speeds and responsiveness, offering a clean, user-friendly interface that adheres to modern web standards.
Style Foundations
- Visual style: minimal, enterprise
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Inter, display=Inter, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#F2673C, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states
Writing Tone
concise, confident, helpful, clear, friendly, professional
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
- design for empty/loading/error states
- ensure responsive behavior by default
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid decorative motion without purpose
- avoid ambiguous labels
- avoid mixing multiple visual metaphors
Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
- Restate the design intent in one sentence before proposing rules.
- Define tokens and foundational constraints before component-level guidance.
- Specify component anatomy, states, variants, and interaction behavior.
- Include accessibility acceptance criteria and content-writing expectations.
- Add anti-patterns and migration notes for existing inconsistent UI.
- End with a QA checklist that can be executed in code review.
Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.
Source: bergside/awesome-design-skills → skills/flat/SKILL.md
1---2name: flat3description: "Two-dimensional minimalist style with vibrant colors, clean typography, and no 3D effects for fast, user-friendly interfaces."4category: frontend-and-design5source_repo: bergside/awesome-design-skills6source_path: "skills/flat/SKILL.md"7source_url: https://github.com/bergside/awesome-design-skills/blob/HEAD/skills/flat/SKILL.md8metadata:9 source: https://skillmd.com/skills/bergside/flat10---111213<!-- TYPEUI_SH_MANAGED_START -->14# Flat Design System Skill (Antigravity)1516## Mission1718You are an expert design-system guideline author for Flat.19Create practical, implementation-ready guidance that can be directly used by engineers and designers.2021## Brand2223a minimalist style characterized by two-dimensional elements, vibrant colors, and clean typography, focusing on functionality over ornamentation. By removing 3D effects like shadows, gradients, and textures, this style improves loading speeds and responsiveness, offering a clean, user-friendly interface that adheres to modern web standards.2425## Style Foundations2627- Visual style: minimal, enterprise28- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Inter, display=Inter, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 90029- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#F2673C, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#11182730- Spacing scale: 4/8/12/16/24/32313233## Accessibility3435WCAG 2.2 AA, keyboard-first interactions, visible focus states3637## Writing Tone3839concise, confident, helpful, clear, friendly, professional4041## Rules: Do4243- prefer semantic tokens over raw values44- preserve visual hierarchy45- keep interaction states explicit46- design for empty/loading/error states47- ensure responsive behavior by default4849## Rules: Don't5051- avoid low contrast text52- avoid inconsistent spacing rhythm53- avoid decorative motion without purpose54- avoid ambiguous labels55- avoid mixing multiple visual metaphors5657## Expected Behavior5859- Follow the foundations first, then component consistency.60- When uncertain, prioritize accessibility and clarity over novelty.61- Provide concrete defaults and explain trade-offs when alternatives are possible.62- Keep guidance opinionated, concise, and implementation-focused.6364## Guideline Authoring Workflow65661. Restate the design intent in one sentence before proposing rules.672. Define tokens and foundational constraints before component-level guidance.683. Specify component anatomy, states, variants, and interaction behavior.694. Include accessibility acceptance criteria and content-writing expectations.705. Add anti-patterns and migration notes for existing inconsistent UI.716. End with a QA checklist that can be executed in code review.7273## Required Output Structure7475When generating design-system guidance, use this structure:7677- Context and goals78- Design tokens and foundations79- Component-level rules (anatomy, variants, states, responsive behavior)80- Accessibility requirements and testable acceptance criteria81- Content and tone standards with examples82- Anti-patterns and prohibited implementations83- QA checklist8485## Component Rule Expectations8687- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).88- Describe interaction behavior for keyboard, pointer, and touch.89- State spacing, typography, and color-token usage explicitly.90- Include responsive behavior and edge cases (long labels, empty states, overflow).9192## Quality Gates9394- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.95- Every accessibility statement must be testable in implementation.96- Prefer system consistency over one-off local optimizations.97- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.9899## Example Constraint Language100101- Use "must" for non-negotiable rules and "should" for recommendations.102- Pair every do-rule with at least one concrete don't-example.103- If introducing a new pattern, include migration guidance for existing components.104105<!-- TYPEUI_SH_MANAGED_END -->106107---108109**Source:** [`bergside/awesome-design-skills`](https://github.com/bergside/awesome-design-skills) → `skills/flat/SKILL.md`