ui-ux-design-intelligence
Provides comprehensive UI/UX design capabilities including design system creation, component design, visual hierarchy, and user-centered design principles. Use when: building design systems, creating visual designs, designing UI components, or establishing design specifications.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- ui-ux-design-intelligence
- owner
- pm
- scope
- common
- status
- active
- version
- 1.0.1
- metadata
- { "type": "implementation", "triggers": [ "design system", "ui design", "ux design", "component design", "visual design", "design tokens", "interface design" ] }
- relates_to
- [ { "type": "follows", "skill": "documentation-writing" } ]
- description
- Provides comprehensive UI/UX design capabilities including design system creation, component design, visual hierarchy, and user-centered design principles. Use when: building design systems, creating visual designs, designing UI components, or establishing design specifications.
- gemini-parity
- skip
- last_reviewed
- 1788652800000
- prerequisites
- none
03 SKILL.md 正文
Context
This skill provides end-to-end UI/UX design capabilities, from design system architecture through component specification. It combines design thinking, visual design principles, and systematic approaches to create cohesive, scalable user interfaces.
When to Use
Design System Creation:
- Trigger: "Create design system" or "Establish design tokens"
- Use Case: Starting new project or redesigning existing system
Component Design:
- Trigger: "Design component" or "Create UI element"
- Use Case: Building individual interface components with specifications
Visual Design:
- Trigger: "Design interface" or "Create visual layout"
- Use Case: Creating screen designs, layouts, or visual compositions
Design Specification:
- Trigger: "Specify design" or "Create design documentation"
- Use Case: Documenting design decisions for handoff to developers
Execution Steps
Step 1: Design System Architecture
Purpose: Establish foundational design system structure.
Design Token Definition:
-
Color System:
- Primary colors (brand colors)
- Secondary colors (supporting colors)
- Semantic colors (success, warning, error, info)
- Neutral colors (grays for text, backgrounds, borders)
- Define color values in HEX, RGB, HSL formats
-
Typography Scale:
- Font families (primary, secondary, code)
- Type scale (heading sizes, body sizes, caption sizes)
- Font weights (light, regular, medium, semibold, bold)
- Line height ratios (body: 1.5-1.7, headings: 1.1-1.3)
- Letter spacing for different sizes
-
Spacing System:
- Base unit (typically 4px or 8px)
- Spacing scale (4, 8, 12, 16, 24, 32, 48, 64, 96 pixels)
- Consistent padding and margins
- Component spacing rules
-
Border Radius:
- Scale for corner radii (0, 4, 8, 16, 24 pixels)
- Usage guidelines for each radius size
- Special cases (circles, pills)
-
Shadows & Elevation:
- Elevation levels (flat, raised, overlay, modal)
- Shadow definitions for each level
- Usage contexts
Output: Design token documentation with all token categories
Step 2: Component Design Principles
Purpose: Create systematic approach to component design.
Component Design Process:
-
Identify Component Purpose:
- What user problem does it solve?
- In what contexts will it be used?
- What are the accessibility requirements?
-
Define Component States:
- Default state
- Hover state
- Focus state (keyboard navigation)
- Active/pressed state
- Disabled state
- Error/invalid state
-
Design Component Variants:
- Size variants (small, medium, large)
- Importance variants (primary, secondary, tertiary)
- Context variants (contained, outlined, text)
-
Specify Component Behavior:
- Interaction patterns
- Animation transitions
- Responsive behavior
- Edge cases
Output: Component specification sheet with all states and variants
Step 3: Visual Hierarchy & Layout
Purpose: Establish clear visual hierarchy and layout systems.
Hierarchy Principles:
-
Size Hierarchy:
- Establish clear size relationships (H1 > H2 > H3 > body)
- Use modular scale for consistent sizing
- Ensure visual distinction between levels
-
Color Hierarchy:
- Primary actions: high contrast, prominent color
- Secondary actions: medium contrast, supporting color
- Tertiary actions: low contrast, minimal color
- De-emphasized actions: neutral/monochrome
-
Spacing Hierarchy:
- More whitespace = more importance
- Group related elements with less spacing
- Separate unrelated elements with more spacing
- Establish vertical rhythm
-
Layout Systems:
- Grid system (columns, gutters, margins)
- Breakpoints for responsive design
- Container max-widths
- Component spacing rules
Output: Layout system documentation with hierarchy guidelines
Step 4: Accessibility & WCAG Compliance
Purpose: Ensure designs meet accessibility standards.
Accessibility Checklist:
-
Color Contrast:
- Text contrast ratio: 4.5:1 (AA) for body text
- Large text contrast ratio: 3:1 (AA) for 18pt+
- Graphic contrast ratio: 3:1 (AA) for UI components
- Test with contrast checker tools
-
Touch Targets:
- Practical baseline: 44×44 CSS pixels (from WCAG 2.5.5 Target Size, Level AAA)
- AA conformance minimum: 24×24 CSS pixels (WCAG 2.5.8, Level AA) — the 44px baseline exceeds it
- Recommended size: 48×48 CSS pixels (tokenized as
--target-sizein tokens.json) - Spacing between touch targets: 8px minimum
-
Typography:
- Base font size: 16px minimum (100%)
- Scalable text units (rem, em, %)
- Line height: 1.5-1.7 for body text
- Paragraph spacing: 1.5× line height
-
Keyboard Navigation:
- Visible focus indicators
- Logical tab order
- Skip navigation links
- No keyboard traps
-
Screen Reader Support:
- Semantic HTML elements
- ARIA labels where needed
- Alt text for images
- Meaningful link text
Output: Accessibility compliance report with remediation steps
Step 5: Design Documentation & Handoff
Purpose: Create comprehensive design specifications for implementation.
Documentation Structure:
-
Component Specification:
- Component name and purpose
- Visual examples (all states and variants)
- Design tokens used
- Spacing and positioning
- Interaction behaviors
- Code examples (CSS, design tokens)
-
Layout Specifications:
- Grid system documentation
- Responsive breakpoints
- Container behaviors
- Spacing utilities
-
Usage Guidelines:
- When to use the component
- When NOT to use the component
- Do's and don'ts
- Common mistakes to avoid
-
Implementation Notes:
- Technical considerations
- Browser compatibility notes
- Performance considerations
- Accessibility requirements
Output: Complete design handoff package with specifications and examples
Step 6: Design Quality Validation
Purpose: Ensure design meets quality standards and best practices.
Validation Checklist:
- [ ] All design tokens defined and documented
- [ ] Component states are complete (default, hover, focus, active, disabled)
- [ ] Color contrast meets WCAG AA standards
- [ ] Touch targets meet minimum size requirements
- [ ] Typography uses proper hierarchy and scale
- [ ] Layout follows grid system
- [ ] Spacing follows spacing system
- [ ] Components work responsively
- [ ] Accessibility considerations addressed
- [ ] Design documentation is complete
- [ ] Implementation examples provided
Quality Gates:
- Design System Review: All tokens defined systematically
- Component Review: All components have complete specifications
- Accessibility Review: WCAG AA compliance verified
- Documentation Review: Handoff documentation is complete
Output: Design quality report with pass/fail status and recommendations
Output Format
For Design System Creation:
- Complete design token system (color, typography, spacing, borders, shadows)
- Design system documentation
- Component library structure
- Usage guidelines
For Component Design:
- Component specification sheet
- Visual examples for all states and variants
- Design token mappings
- Implementation code examples
- Accessibility compliance report
For Visual Design:
- Layout compositions
- Visual hierarchy documentation
- Responsive design specifications
- Grid system documentation
Best Practices
Design System Design: ✅ Do:
- Start with tokens before components
- Use systematic approaches (scales, ratios)
- Document all decisions and rationale
- Test with real content and scenarios
- Iterate based on feedback
❌ Don't:
- Design components without system context
- Skip documentation ("self-documenting" doesn't scale)
- Ignore accessibility or responsive design
- Create arbitrary values without system
- Mix metaphors or paradigms
Component Design: ✅ Do:
- Design for all states upfront
- Consider accessibility from the start
- Use design tokens consistently
- Think about responsive behavior
- Create reusable patterns
❌ Don't:
- Design only the "happy path"
- Add visual treatments arbitrarily
- Hard-code values instead of using tokens
- Ignore mobile or different screen sizes
- Create one-off components without system
Common Mistakes to Avoid
Design System Anti-Patterns:
- Pixel Perfect Fixation: Obsessing over exact pixels instead of systematic relationships
- Token Explosion: Creating too many overly-specific tokens
- Component Sprawl: Designing every possible variant instead of flexible components
- Documentation Debt: Letting documentation fall out of sync with designs
- Accessibility Afterthought: Treating accessibility as optional instead of foundational
Component Design Anti-Patterns:
- State Explosion: Creating too many state combinations
- Hard-Coded Values: Not using design tokens
- Mobile Neglect: Designing only for desktop
- Inconsistency: Not following established patterns
- Over-Engineering: Making components too complex
Related Skills
- service-design: For broader service experience design
- typography-expert: For specialized font and type system design
- accessibility-review: For detailed accessibility auditing
Design Tools Integration
Figma:
- Use design token variables
- Create component variants properly
- Document components with descriptions
- Use auto-layout for responsive components
Design Token Formats:
- Style Dictionary format
- CSS Custom Properties
- Design Tokens JSON
- Figma Variables
Handoff Formats:
- Figma Dev Mode
- Zeplin
- Design token exports
- Code snippets (CSS, React, etc.)
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.