ui-change

Implements frontend UI through design tokens, DESIGN.md contracts, and verifiable component states.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill ui-change-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-change
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/ui-change
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill ui-change-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents writing UI code converge on generic, inconsistent designs because they lack visual memory and taste. This Skill replaces agent guesswork with an executable visual contract: a decided aesthetic tone, design tokens enforced by lint, and a persistent DESIGN.md that survives between sessions. ## Core Features & Use Cases - Tone and token contract: Establishes one named aesthetic direction and routes every color, spacing, radius, shadow, and type value through semantic tokens, with a lint rule rejecting raw hex values outside tokens/. - DESIGN.md as persistent memory: Maintains a living design contract at the frontend root covering typography, colors, spacing rhythm, and the 6 mandatory component states (default, loading, empty, error, hover/focus, disabled). - Anti-drift inventory and numeric UX laws: Inventories existing components before creating new ones and applies measurable rules like 44x44px touch targets, WCAG 2.2 AA contrast, and max one primary button per section. - Use Case: When adding a new settings screen to a React frontend, the agent reads DESIGN.md, reuses inventoried primitives, implements all six states per component, and verifies the anti-hex lint passes before handing off to ui-review. ## Quick Start Use the ui-change skill to design and implement the new dashboard screen following the project's DESIGN.md and design token contract.

Frequently Asked Questions about ui-change

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

FAQPage Schema
How do I stop AI agents from generating generic-looking UI?▼

Define one named aesthetic direction in a DESIGN.md file and route every visual value through semantic design tokens. A lint rule rejecting raw hex values outside tokens/ makes the contract executable rather than advisory.

How to enforce design tokens with lint in a frontend project?▼

Create a lint rule that rejects literal hex values like #RRGGBB and raw spacing values outside the tokens/ directory. The exact lint command is the one declared in the project's AGENTS.md verification section.

What states should every UI component implement?▼

Every component needs six states: default, loading with skeleton or spinner, empty with message and CTA, error with descriptive message and retry, visible hover/focus with outline of at least 2px, and a visually distinct disabled state.

Does this skill install Playwright or accessibility testing tools?▼

No, it never installs tools. Lint, framework, build, and screenshot tools are parametrized in the project's AGENTS.md, and visual verification with screenshots belongs to the sibling ui-review skill.

When should I not create a new UI component?▼

Before creating any component, inventory existing primitives like buttons, inputs, cards, and modals with their import paths. Build screens only from those components and justify any genuinely new one in a single line, since component drift is treated as a bug.