gradient
bergside/awesome-design-skills
Design-system guidance for modern, playful interfaces with smooth color transitions and visual depth.
What is gradient?
Gradient is a design-system skill that provides implementation-ready guidelines for creating cohesive, accessible interfaces using a curated color palette, typography scale, and spacing system. Use it when building component libraries or standardizing UI across teams.
- Defines semantic color tokens (primary, secondary, neutral, success, warning, danger) with WCAG 2.2 AA contrast compliance
- Specifies typography scale (12–36px) with three font families and nine weight options
- Establishes 8pt baseline grid spacing and component anatomy patterns
- Documents component states (default, hover, focus-visible, active, disabled, loading, error) with interaction behavior
- Provides accessibility acceptance criteria including keyboard navigation, 44px+ touch targets, and screen-reader testing
- Includes QA checklists and anti-pattern guidance for code review
How to install gradient
npx skills add https://github.com/bergside/awesome-design-skills --skill gradientHow to use gradient
- 1.Review the style foundations (typography scale, color palette, spacing baseline) to understand the system's constraints
- 2.Use the component rule expectations to author or audit component guidance, defining required states and interaction behavior
- 3.Apply the accessibility requirements checklist to validate keyboard navigation, focus states, and touch-target sizing
- 4.Reference the example constraint language to write clear, testable rules using 'must' and 'should' statements
- 5.Execute the QA checklist during code review to ensure consistency with tokens and foundations
Use cases
- Standardizing a design system across multiple product teams or repositories
- Building accessible component libraries with consistent spacing and typography
- Migrating existing UI to a cohesive token-based design language
- Documenting interaction states and accessibility requirements for engineers and designers
- Creating brand-aligned guidance that balances aesthetics with WCAG 2.2 AA compliance
- Design-system authors and maintainers
- Product engineers implementing component libraries
- Design leads establishing UI consistency across teams
- Accessibility-focused development teams
gradient FAQ
Primary (#990FFA), secondary (#E60076), success (#16A34A), warning (#D97706), danger (#DC2626), surface (#FFFFFF), and text (#111827), plus a 12–36px typography scale and 8pt spacing baseline.
Yes. It enforces WCAG 2.2 AA compliance, keyboard-first interactions, visible focus states, 44px+ touch targets, and semantic HTML before ARIA.
The skill provides a curated foundation (Montserrat, Space Grotesk, JetBrains Mono). You can extend it, but the guidance prioritizes system consistency over local optimizations.
Implementation-ready component guidance including anatomy, states, variants, responsive behavior, accessibility criteria, content standards, anti-patterns, and QA checklists.
The skill prioritizes accessibility. Flag conflicts explicitly and choose the accessible option; document trade-offs in migration notes.
Full instructions (SKILL.md)
Source of truth, from bergside/awesome-design-skills.
name: gradient description: Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth. license: MIT metadata: author: typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->Gradient Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Gradient. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Gradient design style
Style Foundations
- Visual style: modern, playful
- Typography scale: 12/14/16/18/24/30/36 | Fonts: primary=Montserrat, display=Space Grotesk, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#990FFA, secondary=#E60076, 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, semantic HTML before ARIA, screen-reader tested labels, 44px+ touch targets
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.
