Master UI design - visual design, design systems, components, typography, color theory
Creates systematic user interfaces with visual design, components, and design tokens.
/plugin marketplace add pluginagentmarketplace/custom-plugin-ux-design/plugin install custom-plugin-ux-design@pluginagentmarketplace-ux-designThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/config.yamlassets/schema.jsonreferences/GUIDE.mdreferences/PATTERNS.mdscripts/validate.pyAtomic Skill: Create visually compelling and systematic user interfaces
This skill provides structured approaches to visual design, design systems, and component creation.
Skill("custom-plugin-ux-design:ui-design")
interface UIDesignParams {
// Required
task: "visual" | "system" | "component" | "typography" | "color";
scope: string;
// Optional
brand?: {
colors?: string[];
fonts?: string[];
guidelines_url?: string;
};
platform?: "web" | "mobile" | "desktop" | "cross-platform";
constraints?: {
accessibility_level?: "AA" | "AAA";
dark_mode?: boolean;
};
}
task:
type: enum
required: true
values: [visual, system, component, typography, color]
scope:
type: string
required: true
min_length: 5
platform:
type: enum
default: "web"
values: [web, mobile, desktop, cross-platform]
UI DESIGN EXECUTION
────────────────────────────────────────────
Step 1: ANALYZE REQUIREMENTS
├── Parse brand guidelines
├── Identify constraints
└── Define design scope
Step 2: ESTABLISH FOUNDATIONS
├── Define design tokens
├── Set up grid system
└── Create base styles
Step 3: CREATE COMPONENTS
├── Design atomic elements
├── Build component variants
└── Document specifications
Step 4: COMPOSE LAYOUTS
├── Apply visual hierarchy
├── Ensure consistency
└── Optimize for platform
Step 5: VALIDATE & HANDOFF
├── Check accessibility
├── Generate specifications
└── Prepare assets
────────────────────────────────────────────
retry_config:
max_attempts: 3
backoff_type: exponential
initial_delay_ms: 1000
max_delay_ms: 10000
retryable_errors:
- ASSET_GENERATION_FAILED
- TOKEN_SYNC_ERROR
- EXPORT_INTERRUPTED
interface DesignLog {
timestamp: string;
event: "start" | "token_created" | "component_built" | "error" | "complete";
task: string;
tokens_defined: number;
components_created: number;
accessibility_score: number;
}
VISUAL HIERARCHY PRINCIPLES
├── Size and scale
├── Color and contrast
├── Typography weight
├── Spacing and proximity
├── Alignment and grids
└── Visual flow patterns
TOKEN ARCHITECTURE
├── Primitive tokens (raw values)
│ ├── Colors: #hex values
│ ├── Spacing: px/rem values
│ └── Typography: font specs
├── Semantic tokens (purpose)
│ ├── color-text-primary
│ ├── spacing-component-gap
│ └── font-heading-lg
└── Component tokens (scoped)
├── button-background
├── card-padding
└── input-border-color
COMPONENT ANATOMY
├── Base state
├── Hover state
├── Active state
├── Focus state
├── Disabled state
├── Loading state
└── Error state
COMPONENT VARIANTS
├── Size variants (sm, md, lg)
├── Style variants (primary, secondary)
└── Context variants (dark, light)
TYPE SCALE DESIGN
├── Base size selection (16px)
├── Scale ratio (1.25 major third)
├── Heading hierarchy
├── Body text styles
├── Caption and labels
└── Responsive adjustments
FONT PAIRING
├── Primary font (headings)
├── Secondary font (body)
└── Monospace (code)
COLOR ARCHITECTURE
├── Brand colors
│ ├── Primary
│ ├── Secondary
│ └── Accent
├── Neutral palette
│ ├── Gray scale
│ └── Background/surface
├── Semantic colors
│ ├── Success (green)
│ ├── Warning (yellow)
│ ├── Error (red)
│ └── Info (blue)
└── State colors
├── Hover variations
├── Active variations
└── Disabled variations
| Error Code | Description | Recovery |
|---|---|---|
UI-001 | Token undefined | Add to token system |
UI-002 | Contrast failure | Suggest accessible colors |
UI-003 | Component orphaned | Link to design system |
UI-004 | Grid misalignment | Snap to grid |
UI-005 | Asset export failed | Retry with fallback format |
Diagnosis:
├── Check: Token usage
├── Check: Component variants
├── Check: Manual overrides
└── Solution: Audit and standardize
Steps:
1. Extract all style values
2. Compare to token definitions
3. Replace hardcoded values
4. Update component library
Diagnosis:
├── Check: Semantic color mapping
├── Check: Contrast in dark mode
├── Check: Image/icon adaptation
└── Solution: Separate dark tokens
Steps:
1. Create dark mode token set
2. Map semantic colors
3. Test all components
4. Adjust problem areas
describe("UIDesignSkill", () => {
describe("token generation", () => {
it("should create valid color tokens", async () => {
const result = await invoke({
task: "color",
scope: "primary palette"
});
expect(result.tokens.colors).toBeDefined();
expect(result.tokens.colors.primary).toMatch(/^#[0-9A-F]{6}$/i);
});
});
describe("accessibility compliance", () => {
it("should meet AA contrast requirements", async () => {
const result = await invoke({
task: "color",
constraints: { accessibility_level: "AA" }
});
expect(result.contrast_ratio).toBeGreaterThanOrEqual(4.5);
});
});
describe("component specification", () => {
it("should include all states", async () => {
const result = await invoke({
task: "component",
scope: "button"
});
const states = ["default", "hover", "active", "focus", "disabled"];
states.forEach(state => {
expect(result.component.states).toContain(state);
});
});
});
});
| Metric | Target | Measurement |
|---|---|---|
| Token coverage | > 95% | Styles using tokens |
| Accessibility | 100% | AA compliance |
| Component reuse | > 80% | Instances vs customs |
| Consistency score | > 95% | Design audit |
| Version | Date | Changes |
|---|---|---|
| 1.0.0 | 2025-12-30 | Production-grade upgrade |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.