sleek
bergside/awesome-design-skills
Modern minimalist design system with clean lines, intentional colors, and consistent spacing.
What is sleek?
Sleek is a design-system skill for creating modern, minimalist UI with reduced cognitive load. Use it when authoring design guidelines, component specifications, and accessibility-first implementations for engineers and designers.
- Generate implementation-ready design-system guidance with explicit tokens and component rules
- Define semantic color, typography, and spacing foundations using an 8pt baseline grid
- Specify component anatomy, states (default, hover, focus, active, disabled, loading, error), and interaction behavior
- Ensure WCAG 2.2 AA accessibility with keyboard-first interactions and visible focus states
- Document anti-patterns, migration paths, and QA checklists for design consistency
- Provide concise, opinionated rules anchored to tokens and thresholds, not subjective language
How to install sleek
npx skills add https://github.com/bergside/awesome-design-skills --skill sleekHow to use sleek
- 1.Clarify the design intent and goals for the component or system you're documenting
- 2.Define or reference the design tokens (colors, typography, spacing) from the Sleek foundations
- 3.Specify component anatomy, required states, and interaction behavior for keyboard, pointer, and touch
- 4.Write accessibility acceptance criteria that are testable in implementation
- 5.Document content and tone standards with concrete examples
- 6.List anti-patterns and migration guidance for inconsistent existing UI
- 7.Create a QA checklist that can be executed during code review
Use cases
- Author design-system documentation for a new product or design refresh
- Create component specifications (buttons, forms, modals) with explicit state definitions and accessibility criteria
- Establish consistent spacing, typography, and color-token usage across a team or codebase
- Review and improve existing UI for accessibility compliance and visual hierarchy
- Define interaction behavior and responsive breakpoints for keyboard, pointer, and touch input
- Design-system authors and maintainers
- Product designers creating component specifications
- Frontend engineers implementing design tokens and components
- Design leads establishing accessibility and consistency standards
- Teams adopting or migrating to a minimalist design approach
sleek FAQ
Sleek includes a semantic token system: primary (#3B82F6), secondary (#8B5CF6), success (#16A34A), warning (#D97706), danger (#DC2626), surface (#FFFFFF), text (#111827), with typography using Inter (primary/display) and JetBrains Mono (mono) at weights 100–900, and an 8pt baseline spacing grid.
Follow WCAG 2.2 AA standards with keyboard-first interactions, visible focus states, sufficient color contrast, and testable acceptance criteria. Prioritize accessibility over novelty when conflicts arise.
Define required states (default, hover, focus-visible, active, disabled, loading, error), interaction behavior for keyboard/pointer/touch, explicit token usage, responsive behavior, and edge cases like long labels or overflow.
Anchor every rule to a token, threshold, or concrete example. Use 'must' for non-negotiable rules and 'should' for recommendations. Pair every do-rule with at least one don't-example.
Context and goals → design tokens and foundations → component-level rules → accessibility criteria → content standards → anti-patterns → QA checklist.
Full instructions (SKILL.md)
Source of truth, from bergside/awesome-design-skills.
name: sleek description: Modern minimalist aesthetic with clean lines, intentional color palette, subtle interactions, and consistent spacing. license: MIT metadata: author: typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->Sleek Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Sleek. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Sleek UI/UX design emphasizes a modern, minimalist aesthetic ("less is more") focused on clean lines, high functionality, and reduced cognitive load. Key elements include a limited, intentional color palette (e.g., the 60-30-10 rule), subtle, non-distracting interactions, and consistent spacing.
Style Foundations
- Visual style: modern, minimal, clean
- Typography scale: desktop-first expressive scale | 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=#3B82F6, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 8pt baseline grid
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states
Writing Tone
concise, confident, helpful
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels
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.
Related skills
More from bergside/awesome-design-skills and the wider catalog.
