button-states

Generate six-state UI component systems with algorithmic color derivations.

Updated May 24, 2026
One-click install
npx skills add https://github.com/yonetim258852/ozgur-os --skill button-states
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: button-states
Source: https://github.com/yonetim258852/ozgur-os/tree/main/.claude/skills/button-states
Command: npx skills add https://github.com/yonetim258852/ozgur-os --skill button-states

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI designers often miss complete state coverage for interactive elements, resulting in inconsistent behavior and jarring user experiences. This Skill ensures every interactive element has a complete, six-state definition (rest, hover, active/pressed, focus, disabled, and loading) with algorithmic color derivations to maintain consistency across the design system.

Core Features & Use Cases

  • Six defined states for buttons, links, inputs, and other clickable elements, all derived from a base color.
  • Deterministic hover and active color variations that stay coherent across themes.
  • Focus outlines that meet accessibility guidelines and do not rely on hover alone.

Quick Start

Design a complete six-state system for all interactive elements and derive hover/active colors algorithmically from a base color.

Frequently Asked Questions about button-states

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

FAQPage Schema
How do I define complete button states for a design system?

To define complete button states for a design system, you create a six-state definition covering rest, hover, active, focus, disabled, and loading. This ensures consistent behavior across buttons, links, inputs, and clickable elements by deriving all state variations algorithmically from a single base color.

How do I enforce accessible focus outlines for interactive elements?

To enforce accessible focus outlines, you apply distinct focus states using the CSS outline property rather than relying on hover alone. This approach meets accessibility guidelines by clearly indicating interactive elements like buttons and inputs during keyboard navigation.

Can I apply these interactive state rules to inputs and links?

Yes, you can apply this six-state interactive system to inputs, links, and other clickable elements beyond standard buttons. The state derivation logic scales across all interactive UI components to ensure consistent user experience and accessible contrast throughout the interface.

Why do my UI components have inconsistent hover and active states?

Inconsistent hover and active states usually occur when UI designers miss complete state coverage and manually pick colors. Automating state derivation from a base color solves this jarring user experience by applying deterministic color variations across the entire design system.