Claude Code Plugins

Community-maintained marketplace

Feedback

Modern UI/UX design principles for minimalist, efficient, and elegant interfaces. Covers keyboard-driven design, command palettes, component architecture, accessibility, and performance. Based on analysis of Linear, Raycast, Arc, and other top-tier developer tools in 2025. Use when designing UI components, planning features, or reviewing interface design decisions.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name ui-ux-principles
description Modern UI/UX design principles for minimalist, efficient, and elegant interfaces. Covers keyboard-driven design, command palettes, component architecture, accessibility, and performance. Based on analysis of Linear, Raycast, Arc, and other top-tier developer tools in 2025. Use when designing UI components, planning features, or reviewing interface design decisions.
allowed-tools Read, Grep, Write, Edit

Modern UI/UX Design Principles - 2025

Core Philosophy

"Simplicity is the ultimate sophistication." - Leonardo da Vinci

Modern UI/UX design in 2025 is defined by functional reduction aligned with technical performance, moving beyond mere visual simplicity to create genuinely efficient user experiences.


1. Minimalism Principles

1.1 Functional Reduction

  • Less is More: Include only elements that serve a clear purpose
  • Every element must justify its existence: If it doesn't add value, remove it
  • Eliminate decorative elements: Focus on content and functionality

1.2 White Space Strategy

  • Negative space as power: Use ample white space to highlight essential elements
  • Breathing room: Create visual hierarchy through spacing, not lines
  • Cognitive load reduction: White space improves focus and comprehension

1.3 Technical Minimalism

  • Performance-first: Optimize SVGs for GPU, lazy-load components
  • Skeleton screens: Show structure while content loads
  • Micro-functional UI: Replace monolithic pages with adaptive components

2. Efficiency-First Design

2.1 Keyboard-Driven Interface

  • Shortcuts are fastest: Keyboard > Mouse > Touch
  • Command palette pattern: Cmd+K for universal action access (Linear, Raycast)
  • Discoverability: Show shortcuts on hover (2-3 second delay)
  • Fuzzy search: Be forgiving with typos and partial matches

2.2 Command Palette Best Practices

✓ Include all menu and context actions
✓ Display associated hotkeys
✓ Support aliases for frequently used commands
✓ Group related actions with sections
✓ Show loading states for async operations
✗ Don't overwhelm with low-level system utilities by default

2.3 Interaction Minimization

  • Reduce steps: Fewest steps to complete core tasks
  • Automate decisions: Make smart defaults instead of asking
  • Inline actions: Edit in place, don't open dialogs
  • Progressive disclosure: Show complexity only when needed

3. Developer Tools UX

3.1 Developer-Centric Principles

  • Functionality over aesthetics: Think Vim/Sublime, not flashy interfaces
  • Efficiency is beauty: Speed is the most important feature
  • Adjustability: Let users customize workflows
  • Power user features: Expert shortcuts and advanced modes

3.2 Visual Minimalism for Devs

  • Minimal color palette: Neutral base + single accent color
  • Functional colors only: Green/Red/Yellow for status/trends, not decoration
  • Classic readable fonts: System fonts (SF, Roboto, Segoe UI)
  • No distractions: Remove anything that doesn't serve a purpose

3.3 Information Architecture

  • High information density: Organize lots of data without clutter
  • Visual grouping: Cards, sections, heatmaps for organization
  • Trend visualization: Show changes over time clearly
  • Context awareness: Adapt interface based on user's current task

4. Component Architecture

4.1 Atomic Design Hierarchy (2025 Evolution)

Ions → Atoms → Molecules → Organisms → Templates → Pages
(Design tokens) → (Basic elements) → (Simple combinations) →
(Complex components) → (Layouts) → (Final instances)

Key Updates for 2025:

  • Flexible hierarchy: Not strictly rigid, use semantics over categories
  • Design tokens: Single source of truth for colors, spacing, typography
  • Behavioral patterns: Interaction logic (modals, confirmations) as components

4.2 Consistency Strategy

  • Design tokens first: Define values before components
  • Component composition: Build complex UIs from simple, reusable parts
  • Style guides: Document patterns, not just components
  • Cross-platform consistency: Tokens ensure unity across web, desktop, mobile

5. Typography & Visual Design

5.1 Typography Principles

  • One typeface: Use system fonts, play with weight/style/size
  • Clear hierarchy: Size, weight, and color create visual order
  • Legibility first: Never sacrifice readability for aesthetics
  • Line length: 60-75 characters for optimal readability
  • Line height: 1.5-1.7 for body text

5.2 Color Strategy

  • Monochromatic base: Neutral grays for structure
  • Single accent: One color for primary actions/brand
  • Functional colors: Status colors have specific meanings
    • Green: Success/complete
    • Red: Error/delete
    • Yellow: Warning/pending
    • Blue: Info/neutral
  • Dark mode: Essential feature, not afterthought
  • High contrast: Ensure WCAG AA compliance (4.5:1 for text)

5.3 Visual Hierarchy

  • Size hierarchy: Larger = more important
  • Color weight: Darker/bolder = higher priority
  • Position: Top/left = primary (in LTR languages)
  • No zig-zag: One-dimensional scrolling when possible
  • Alignment: Consistent alignment creates structure

6. Performance & Responsiveness

6.1 Speed as a Feature

  • Perceived performance: Show progress immediately
  • Streaming responses: Display content as it arrives
  • Optimize first paint: Above-fold content loads first
  • Defer non-critical: Load secondary content after main interface

6.2 Adaptive Interfaces

  • Context-aware layouts: Adjust based on screen size and user state
  • Device continuity: Seamless experience across devices
  • Responsive by default: Mobile-first approach
  • Touch-friendly: Minimum 44x44px tap targets

6.3 Loading States

  • Skeleton screens: Show structure, don't spin
  • Progressive loading: Load content in priority order
  • Optimistic UI: Show expected result, rollback on error
  • Error boundaries: Graceful degradation

7. Interaction Patterns

7.1 Micro-interactions

  • Subtle animations: 200-300ms transitions
  • Purposeful motion: Every animation has meaning
  • Fluid like water: Soft, natural timing curves (ease-out)
  • Status feedback: Instant response to every action

7.2 Feedback Loops

  • Immediate acknowledgment: Show action registered
  • Progress indication: Long operations show progress
  • Clear completion: Confirm when task finishes
  • Error handling: Explain what went wrong and how to fix

7.3 Common Patterns

  • Command palette: Universal action access
  • Inline editing: Edit without modal dialogs
  • Context menus: Right-click for actions
  • Keyboard navigation: Full keyboard support
  • Undo/redo: Make actions reversible

8. Accessibility & Inclusivity

8.1 WCAG Standards

  • Color contrast: Minimum 4.5:1 for normal text
  • Keyboard navigation: All features accessible via keyboard
  • Screen reader support: Proper ARIA labels and semantics
  • Focus indicators: Visible focus states (never outline: none)

8.2 Inclusive Design

  • Design for extremes: If it works for disabilities, it works for everyone
  • Color blindness: Don't rely on color alone to convey meaning
  • Motion preferences: Respect prefers-reduced-motion
  • Text sizing: Support 200% zoom without breaking layout

9. Design System Integration

9.1 Design Token Structure

/* Semantic, not presentational */
--color-bg-primary: not --color-gray-50
--color-text-default: not --color-black
--spacing-unit: not --spacing-8px
--font-size-body: not --font-size-16px

9.2 Component Guidelines

  • Single responsibility: Each component does one thing well
  • Composable: Combine components to build complex UIs
  • Configurable: Props control behavior, not styles
  • Documented: Examples, not just descriptions

9.3 Consistency Enforcement

  • Linting tools: Automated style checking
  • Code review: Human verification
  • Design reviews: Regular UI/UX audits
  • User testing: Validate with real users

10. Metrics & Validation

10.1 Quantitative Metrics

  • Task completion rate: % users who complete core tasks
  • Time to completion: Average time for key workflows
  • Error rate: Frequency of user errors
  • NPS/Satisfaction: User happiness scores

10.2 Qualitative Validation

  • User interviews: Talk to actual users regularly
  • Usability testing: Observe real usage patterns
  • A/B testing: Compare design alternatives
  • Heatmaps/analytics: See how users interact

10.3 Continuous Improvement

  • Data-driven decisions: Use metrics to guide changes
  • Iterate quickly: Ship, measure, improve
  • User feedback loops: Easy way to report issues
  • Regular audits: Periodic UX reviews

11. Anti-Patterns to Avoid

11.1 Common Mistakes

  • ❌ Feature bloat: Adding features without clear user need
  • ❌ Inconsistent patterns: Different ways to do same thing
  • ❌ Over-animation: Motion that distracts or slows users
  • ❌ Modal fatigue: Too many popups and dialogs
  • ❌ Hidden functionality: Features users can't discover

11.2 Red Flags

  • ⚠️ Users need training: Interface should be self-explanatory
  • ⚠️ Multiple clicks for common tasks: Optimize frequent workflows
  • ⚠️ Visual clutter: Too much competing for attention
  • ⚠️ Slow performance: Users notice >100ms delays
  • ⚠️ Accessibility issues: Excluding users is unacceptable

12. Modern Tool Examples

12.1 Reference Applications

  • Linear: Keyboard-driven, minimal UI, blazing fast
  • Raycast: Command palette, extensible, developer-focused
  • Arc: Spatial organization, visual delight, power features
  • Notion: Block-based, flexible, clean hierarchy
  • VS Code: Keyboard shortcuts, command palette, extensions

12.2 Common Patterns

  • Cmd+K: Command palette
  • Cmd/Ctrl+P: Quick open
  • /: Command mode in editors
  • G + key: Navigate to section (vim-style)
  • Esc: Clear selection/go back

13. Implementation Checklist

13.1 Pre-Design

  • Define core user goals
  • Identify key workflows
  • Research user mental models
  • Establish performance budgets

13.2 Design Phase

  • Create design tokens first
  • Build component library
  • Document patterns
  • Test with real users

13.3 Development

  • Implement keyboard navigation
  • Add loading/error states
  • Ensure accessibility
  • Optimize performance

13.4 Launch & Iterate

  • Monitor usage metrics
  • Gather user feedback
  • A/B test improvements
  • Regular UX audits

14. Quick Reference: Design Decision Framework

When making design decisions, ask:

  1. Purpose: What problem does this solve?
  2. Necessity: Is this essential for the core task?
  3. Simplicity: Can we make it simpler?
  4. Efficiency: Is this the fastest way?
  5. Accessibility: Can everyone use this?
  6. Performance: Will this slow things down?
  7. Consistency: Does this match existing patterns?
  8. Maintainability: Can we sustain this long-term?

If the answer to any of these is negative, reconsider the design.


Sources