energetic

Define energetic design-system tokens, component states, and WCAG 2.2 AA focus rules.

2.3k|211|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bergside/awesome-design-skills --skill energetic-bergside
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: energetic
Source: https://github.com/bergside/awesome-design-skills/tree/main/skills/energetic
Command: npx skills add https://github.com/bergside/awesome-design-skills --skill energetic-bergside

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves inconsistent UI styling by providing concrete, implementation-ready guidelines for a vibrant, high-contrast “energetic” design language.

Core Features & Use Cases

  • Tokenized styling foundations: Defines primary/secondary/background/surface/text/neutral colors, typography scale (12/14/16/20/24/32/48), and spacing/border rhythm (including signature 4px thick borders).
  • Component-ready rules: Specifies how to implement hierarchy, interaction states, spacing/typography usage, and responsive/edge-case behavior.
  • Accessibility and quality gates: Enforces WCAG 2.2 AA principles (keyboard-first, visible focus) with testable acceptance criteria and QA checklists.

Quick Start

Ask an AI to generate an Energetic-themed component set using the provided tokens, thick 4px border rules, and explicit default/hover/focus-visible/active/disabled/error states.

Frequently Asked Questions about energetic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a high-contrast UI design system that meets WCAG 2.2 AA accessibility standards?

Create a high-contrast UI design system by defining explicit keyboard-first focus-visible behavior, testable acceptance criteria, and a tokenized color and typography scale to enforce WCAG 2.2 AA compliance across all interaction states.

What are design tokens for thick border UI components and how do I implement them?

Design tokens for thick border UI components define primary, secondary, background, surface, text, and neutral colors alongside a spacing and border rhythm with signature 4px borders. Implement them by applying these tokens to containers, inputs, and cards for consistent styling.

How do I standardize interaction states across web UI components using a design system?

Standardize interaction states across web UI components by specifying concrete rules for default, hover, focus-visible, active, disabled, and error states. Apply tokenized styling foundations to ensure consistent hierarchy and responsive behavior across navigation and cards.

Can I use these energetic design system rules for existing component libraries?

Yes, you can apply energetic design system rules to existing component libraries by mapping your current elements to the provided typography scale, spacing rhythm, and 4px thick border guidelines to ensure accessible implementation and consistent visual hierarchy.

What is the best way to ensure consistent styling and accessibility for high-contrast web UI patterns?

The best way to ensure consistent styling and accessibility for high-contrast web UI patterns is to use token-first guidance with explicit component anatomy rules and QA checklists that enforce keyboard-first navigation and visible focus alignment.

What typography scale and spacing rhythm should I use for an accessible design system?

Use a typography scale of 12, 14, 16, 20, 24, 32, and 48px paired with a defined spacing and border rhythm that includes signature 4px thick borders to establish vibrant, accessible foundations for your UI components.