flux-design-system

Define and enforce a grayscale design system for Flux UI components.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/lyzno1/flux --skill flux-design-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flux-design-system
Source: https://github.com/lyzno1/flux/tree/main/.agents/skills/flux-design-system
Command: npx skills add https://github.com/lyzno1/flux --skill flux-design-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Flux UI components lack a unified design language, causing visual inconsistency and slower collaboration. This design system defines grayscale tokens, elevation, spacing, and shape semantics to ensure cohesive, accessible interfaces across the Flux web app.

Core Features & Use Cases

  • Token-driven grayscale color system (oklch) for backgrounds, surfaces, borders, and text to maintain visual harmony.
  • Shape and depth rules: rounded radii and elevation tokens guide component styling for buttons, cards, dialogs, and menus.
  • Theming and accessibility: auto-switching between light and dark modes without hardcoded colors, ensuring WCAG-compliant contrast.
  • Review and governance: provides a reference framework for designers and engineers to audit UI consistency.

Quick Start

Review a UI component and map its colors, radii, and elevations to Flux tokens, then update the component to align with the design system. For example, replace hard-coded colors with the corresponding tokens and apply rounded-xl or rounded-full where appropriate.

Frequently Asked Questions about flux-design-system

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

FAQPage Schema
What is a token-based design system for UI components?

Grayscale UI tokens use the oklch color space to define backgrounds, surfaces, borders, and text. This token-based approach maintains visual harmony across components while supporting WCAG-compliant contrast and auto-switching between light and dark modes.

How do I apply design tokens to Flux UI components?

To apply design tokens, review a UI component and map its hardcoded colors, radii, and elevations to the corresponding Flux tokens. Update the component styling to use these tokens, applying shapes like rounded-xl or rounded-full where appropriate for consistency.

Can I auto-switch between light and dark modes without hardcoded colors?

Yes, you can auto-switch between light and dark modes by using token-based colors instead of hardcoded values. The system applies oklch grayscale tokens for surfaces and text, ensuring accessibility and WCAG-compliant contrast across themes automatically.

Does the Flux design system support accessibility and WCAG compliance?

The Flux design system supports accessibility by using oklch grayscale tokens that ensure WCAG-compliant contrast. It enforces auto-switching between light and dark modes without hardcoded colors, maintaining accessible interfaces across all core components.

What are the limitations of using a grayscale design system for UI?

A grayscale design system focuses solely on neutral color palettes, limiting vibrant or brand-specific color expressions. It governs radii, elevation, and spacing for consistency, but multi-hue branding requires extending the token framework beyond its core scope.