vibrant
bergside/awesome-design-skills
Lively, colorful design system with bold typography, warm accents, and dynamic visual energy.
What is vibrant?
Vibrant is a design-system skill for creating modern, clean, and playful user interfaces. Use it when you need to author implementation-ready design guidelines with consistent typography, color tokens, spacing scales, and accessibility standards (WCAG 2.2 AA).
- Define and document design tokens (color, typography, spacing) with semantic naming
- Create component-level rules covering anatomy, states, variants, and responsive behavior
- Establish accessibility requirements (keyboard navigation, focus states, screen-reader labels, 44px+ touch targets)
- Author content and tone standards aligned to brand voice
- Identify anti-patterns and provide migration guidance for inconsistent UI
- Generate QA checklists for design-system implementation review
How to install vibrant
npx skills add https://github.com/bergside/awesome-design-skills --skill vibrantHow to use vibrant
- 1.Install the skill using the provided npm command
- 2.Identify the component or pattern you need to document (e.g., buttons, forms, navigation)
- 3.Restate the design intent in one sentence before proposing rules
- 4.Define applicable design tokens (color, typography, spacing) from the Vibrant palette
- 5.Specify component anatomy, required states (default, hover, focus, active, disabled, loading, error), and interaction behavior for keyboard, pointer, and touch
- 6.Include testable accessibility acceptance criteria (contrast ratios, focus indicators, screen-reader labels)
- 7.Document content and tone standards with concrete examples
- 8.List anti-patterns and migration guidance for existing inconsistent implementations
Use cases
- Building a cohesive design system for a product team with shared component guidelines
- Documenting typography scales, color palettes, and spacing rhythms for engineers and designers
- Ensuring WCAG 2.2 AA accessibility compliance across all UI components
- Creating component state matrices (default, hover, focus, active, disabled, loading, error)
- Establishing design-token naming conventions and preventing low-contrast or inconsistent spacing
- Design-system authors and maintainers
- Product designers creating implementation-ready specifications
- Engineers building component libraries
- Teams standardizing UI consistency across products
vibrant FAQ
Vibrant provides typography (Noto Sans primary, Fascinate display, Fira Code mono), color tokens (primary #7C61D4, secondary #EAAE87, success #16A34A, warning #D97706, danger #DC2626, surface #FFFFFF, text #2F281D), and spacing scale (2/4/8/12/16/24/32/48).
Yes. Vibrant requires WCAG 2.2 AA compliance, keyboard-first interactions, visible focus states, screen-reader tested labels, reduced-motion support, and 44px+ touch targets.
Define all relevant states explicitly: default, hover, focus-visible, active, disabled, loading, and error. Specify spacing, typography, and color-token usage for each state.
Prioritize accessibility. Flag the conflict, explain the trade-off, and choose the accessible option.
No. Vibrant requires semantic tokens over raw values to maintain consistency and enable system-wide updates.
Full instructions (SKILL.md)
Source of truth, from bergside/awesome-design-skills.
name: vibrant description: Lively, colorful design with bold playful typography, warm accents, and dynamic visual energy. license: MIT metadata: author: typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->Vibrant Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Vibrant. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Vibrant style
Style Foundations
- Visual style: modern, clean, bold, playful
- Typography scale: 14/16/18/24/32/40 | Fonts: primary=Noto Sans, display=Fascinate, mono=Fira Code | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, neutral, success | Tokens: primary=#7C61D4, secondary=#EAAE87, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#2F281D
- Spacing scale: 2/4/8/12/16/24/32/48
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support
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.

