home / skills / eyadsibai / ltk / ui-ux

This skill guides UI and UX decisions, helping you design usable interfaces with consistent layout, typography, and responsive patterns.

npx playbooks add skill eyadsibai/ltk --skill ui-ux

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
4.3 KB
---
name: UI/UX Design
description: This skill should be used when the user asks about "UI design", "UX design", "user interface", "user experience", "wireframes", "mockups", "design patterns", "design system", "component design", "layout", or mentions UI/UX decisions.
version: 1.0.0
---

# UI/UX Design

Guidance for user interface and user experience design decisions.

## Core Principles

### Visual Hierarchy

Establish clear importance levels:

1. **Size**: Larger elements draw attention first
2. **Color**: Contrast guides the eye
3. **Spacing**: White space creates groupings
4. **Position**: Top-left reads first (in LTR languages)

### Consistency

- Use consistent spacing scale (4px, 8px, 16px, 24px, 32px, 48px)
- Maintain consistent component patterns
- Follow platform conventions (Material, iOS, Web)

### Feedback

Every action needs feedback:

- **Immediate**: Button press states
- **Progress**: Loading indicators
- **Completion**: Success/error messages

## Layout Patterns

### Card Layout

```
┌─────────────────┐
│     Image       │
├─────────────────┤
│ Title           │
│ Description     │
│ [Action Button] │
└─────────────────┘
```

Use for: Collections, products, articles

### List Layout

```
┌──┬──────────────┐
│##│ Title        │
│  │ Subtitle     │
└──┴──────────────┘
```

Use for: Settings, navigation, data tables

### Dashboard Layout

```
┌────────┬────────┬────────┐
│ Metric │ Metric │ Metric │
├────────┴────────┴────────┤
│      Main Chart          │
├─────────────┬────────────┤
│   Table     │  Activity  │
└─────────────┴────────────┘
```

## Component Design

### Buttons

| Type | Use Case |
|------|----------|
| Primary | Main action (1 per view) |
| Secondary | Alternative actions |
| Tertiary/Ghost | Low-emphasis actions |
| Destructive | Delete, remove actions |

### Forms

- Label above input (not placeholder-only)
- Show validation inline
- Group related fields
- Mark optional fields, not required
- Provide helpful error messages

### Navigation

- **Top nav**: Global, persistent
- **Side nav**: Complex apps, many sections
- **Bottom nav**: Mobile, 3-5 items max
- **Breadcrumbs**: Deep hierarchies

## Responsive Design

### Breakpoints

```css
/* Mobile first */
/* Default: Mobile (< 640px) */
@media (min-width: 640px)  { /* Tablet */ }
@media (min-width: 1024px) { /* Desktop */ }
@media (min-width: 1280px) { /* Large desktop */ }
```

### Adaptation Strategies

- **Stack**: Columns become rows on mobile
- **Hide**: Show/hide elements by importance
- **Resize**: Proportional scaling
- **Reflow**: Different layouts per breakpoint

## Color Usage

### Semantic Colors

| Color | Meaning |
|-------|---------|
| Blue | Primary actions, links |
| Green | Success, positive |
| Yellow/Orange | Warning, attention |
| Red | Error, destructive |
| Gray | Neutral, disabled |

### Contrast Requirements

- Text on background: 4.5:1 minimum (WCAG AA)
- Large text: 3:1 minimum
- Interactive elements: 3:1 minimum

## Typography

### Scale

```
xs:  12px  - Labels, captions
sm:  14px  - Body small
base: 16px - Body default
lg:  18px  - Body large
xl:  20px  - Heading small
2xl: 24px  - Heading medium
3xl: 30px  - Heading large
4xl: 36px  - Display
```

### Line Height

- Headings: 1.2 - 1.3
- Body text: 1.5 - 1.6
- UI elements: 1.0 - 1.25

## UX Patterns

### Empty States

Show when no data:

- Friendly illustration
- Explain what goes here
- Provide action to add first item

### Loading States

- Skeleton screens > spinners
- Progressive loading
- Optimistic UI when safe

### Error Handling

- Explain what went wrong
- Suggest how to fix
- Provide recovery action
- Don't blame the user

## Design Checklist

- [ ] Clear visual hierarchy
- [ ] Consistent spacing and alignment
- [ ] Responsive across devices
- [ ] Accessible color contrast
- [ ] Clear interactive states
- [ ] Helpful error messages
- [ ] Loading feedback
- [ ] Empty state design

Overview

This skill provides practical guidance for UI and UX design decisions, covering layout patterns, components, responsiveness, color, typography, and interaction feedback. It distills core principles like visual hierarchy, consistency, and accessible feedback into actionable rules you can apply to web and mobile interfaces. Use it to validate design choices, create wireframes, or review component behavior for usability and accessibility.

How this skill works

The skill inspects common UI/UX concerns and recommends patterns and rules based on context: layout type (card, list, dashboard), component purpose (buttons, forms, navigation), and device breakpoints. It highlights accessibility thresholds (contrast ratios, typography scale), interaction feedback needs (immediate, progress, completion), and responsive adaptation strategies (stack, hide, resize, reflow). It returns concrete, prioritized suggestions you can apply directly in designs or hand off to engineers.

When to use it

  • Designing or reviewing wireframes and mockups
  • Choosing patterns for navigation, forms, buttons, or layout
  • Making responsive decisions for mobile, tablet, and desktop
  • Improving accessibility and color contrast for text and UI elements
  • Defining component behavior and feedback for user actions

Best practices

  • Establish a clear visual hierarchy using size, color, spacing, and position
  • Use a consistent spacing scale and component patterns across views
  • Provide immediate and meaningful feedback for every user action (states, loaders, confirmations)
  • Follow platform conventions (Material, iOS, web) and limit surprises
  • Design mobile-first and apply clear breakpoint strategies (stack, hide, resize, reflow)

Example use cases

  • Create a product card layout for a catalog with clear image, title, description, and primary CTA
  • Design a settings list using a compact list layout with titles and subtitles
  • Build a dashboard with top metrics, a main chart, and secondary tables/activity panels
  • Design a form with labels above inputs, inline validation, and helpful error messages
  • Improve an app’s empty state with an illustration, explanation, and primary action button

FAQ

What contrast ratio should I use for readable text?

Aim for 4.5:1 for normal text and 3:1 for large text to meet WCAG AA.

How many top-level navigation items are appropriate on mobile?

Use bottom navigation with 3–5 items max; more items dilute discoverability.