kb-design-system

Enforce design-system consistency by auditing UI against token and kit rules.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill kb-design-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-design-system
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/kb-design-system
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill kb-design-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents inconsistent, theme-breaking UI by enforcing a universal design-system discipline: tokens over literals, kit reuse over inline styling, and coherent typography, spacing, shadows, and colors across every theme.

Core Features & Use Cases

  • Token discipline: Require colors, spacing, radii, and shadows to come only from the system (no hardcoded values).
  • Component-kit reuse: Prefer kit components and extend the kit when something is missing, rather than styling raw elements ad hoc.
  • Scale and multi-theme consistency: Catch scale drift (mixed radii/spacing/shadows) and verify coherence in every defined theme.
  • Design review guardrails: Provide review checklists and anti-patterns for UI audits.
  • UX law integration: Apply Hick’s, Fitts’, Miller’s, and related laws to support better interface decisions.

Quick Start

When reviewing a screen for visual consistency, ask the AI to audit it against token usage, kit reuse, scale rules, multi-theme coherence, typography scale, and the 60-30-10 color guideline.

Frequently Asked Questions about kb-design-system

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

FAQPage Schema
How do I enforce design system consistency and eliminate hardcoded UI values?

To enforce design system consistency, you must eliminate hardcoded UI values by auditing screens against a token-first governance model. This requires colors, spacing, radii, and shadows to come only from the system, preventing theme-breaking inconsistencies.

What is the best way to audit UI for token usage and component-kit reuse?

The best way to audit UI for token usage is to review screens against a checklist for kit reuse and token discipline. This catches scale drift and prevents kit bypass, ensuring raw elements are not styled ad hoc instead of using existing components.

How do I check my interface for typography scale and 60-30-10 color rule compliance?

To check interface compliance with typography scale and the 60-30-10 color rule, audit the UI against core UX heuristics. This verifies readable typographic scaling and ensures color distribution follows the designated proportional system.

Does this design system governance approach support multi-theme verification?

Yes, this design system governance approach supports multi-theme verification. It checks scale drift across mixed radii, spacing, and shadows, verifying coherence in every defined theme to prevent visual inconsistencies.

When should I extend the component inventory instead of styling raw elements ad hoc?

You should extend the component inventory when a required UI element is missing from the kit. This prevents kit bypass during implementation reviews, ensuring component-kit reuse is preferred over inline styling for ad hoc raw elements.

How do UX heuristics like Hick's and Fitts' laws integrate into UI design reviews?

UX heuristics like Hick's, Fitts', and Miller's laws integrate into UI design reviews by acting as guardrails. Applying these laws supports better interface decisions and ensures the design satisfies core usability rules.