---
name: ui-ux-design
description: Comprehensive UI/UX design — user research, wireframes, mockups, prototyping, and design review. Invoke for new feature design, page redesign, UX audit, or user flow planning.
user-invocable: true
title: ui-ux-design
canonical_url: https://skilld.dev/gh/colaberryintern/colaberryenterprise_ai_leadershipaccelerator/ui-ux-design
last_updated: 2026-10-08T09:39:34.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install colaberryintern/colaberryenterprise_ai_leadershipaccelerator/ui-ux-design`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/ui-ux-design`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/colaberryintern/colaberryenterprise_ai_leadershipaccelerator/ui-ux-design) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/ui-ux-design`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/ui-ux-design --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/ui-ux-design --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# UI/UX Design — Strategy, Research & Prototyping

## When to Use This Skill vs /frontend-design

| Use `/ui-ux-design` for | Use `/frontend-design` for |
|---|---|
| New feature exploration & ideation | Implementing a specific component |
| Page redesign research | Writing the actual React code |
| UX audit & heuristic evaluation | Modifying an existing page |
| User flow mapping | Adding a table, form, or card |
| Wireframing & layout planning | Styling adjustments |
| Design review & critique | Bug fixes in UI |

This skill is **strategic and exploratory**. Use `/frontend-design` when you're ready to write code.

---

## Target Audience

**Primary persona**: Enterprise executives, aged 35–60
- Tech-savvy but time-constrained
- Values: clarity, authority, professionalism
- Scans before reading — needs scannable information density
- Prefers clean, calm, authoritative interfaces over flashy/trendy
- Expects mobile access but primarily uses desktop

**Design tone**: Clean, calm, authoritative. Think Bloomberg Terminal meets Salesforce, not consumer SaaS.

---

## Design Principles

### 1. Progressive Disclosure
- Show summary first, detail on demand
- Use tabs, modals, and expandable sections
- KPI cards at top → detailed tables/charts below
- Don't overwhelm with data — let users drill down

### 2. Scannable Information Density
- Bold numbers for metrics, muted labels below
- Status badges for quick visual scanning
- Consistent color coding (green=good, red=attention, yellow=warning)
- Use whitespace generously — padding is not waste

### 3. Consistent Visual Language
- Every page follows the same card → table → modal hierarchy
- Same filter bar pattern across all list views
- Same badge styles for status, temperature, and type indicators
- Same loading spinner placement (centered, with primary color)

### 4. Predictable Interactions
- Click name → detail modal or detail page
- Click badge/status → filter by that value
- Bulk select via checkboxes → action bar appears
- Cancel/close always top-right or bottom-left

### 5. Error Prevention Over Error Handling
- Disable buttons when action isn't available
- Confirm destructive actions (delete, remove)
- Show validation inline, not after submission
- Gray out impossible states

---

## Capabilities

### User Research
- Define user personas and scenarios
- Map user journeys through the application
- Identify pain points and opportunities
- Competitive analysis of similar tools

### Wireframing
Create ASCII wireframes for layout exploration:

```
┌──────────────────────────────────────────────────┐
│ Page Title                        [Action] [More]│
├──────────────────────────────────────────────────┤
│ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐                │
│ │ KPI │ │ KPI │ │ KPI │ │ KPI │                │
│ │  42 │ │ 87% │ │ $12K│ │  8  │                │
│ └─────┘ └─────┘ └─────┘ └─────┘                │
│                                                  │
│ [Search...] [Filter ▼] [Filter ▼]    [+ Add]    │
│                                                  │
│ ┌────────────────────────────────────────────┐   │
│ │ □  Name       Company    Score  Status     │   │
│ │ □  John Doe   Acme Inc   85     ●Active    │   │
│ │ □  Jane Smith BigCo      72     ○Paused    │   │
│ └────────────────────────────────────────────┘   │
│                          [← Prev] Page 1 [Next →]│
└──────────────────────────────────────────────────┘
```

### React Mockup Generation
Generate functional React components with realistic mock data for visual review before wiring up to the backend.

### Design Review
Evaluate existing pages against:
- The 5 design principles above
- WCAG 2.1 AA accessibility (delegate to `/fixing-accessibility` for detailed audit)
- Responsive behavior at all breakpoints
- Visual consistency with the design system

---

## Responsive Checkpoints

Test and consider layouts at these widths:

| Breakpoint | Width | Device | Key considerations |
|---|---|---|---|
| Mobile | 320px | Small phone | Single column, stacked cards, hamburger nav |
| Mobile | 375px | iPhone SE/13 | Most common mobile width |
| Tablet | 768px | iPad portrait | 2-column grid, condensed tables |
| Desktop | 1024px | Laptop | Full sidebar + content |
| Wide | 1920px | External monitor | Max-width container, no stretch |

---

## Design Deliverables

When invoked for a design task, provide:

1. **Context**: What problem are we solving? Who is the user?
2. **User flow**: Step-by-step journey through the feature
3. **Wireframe**: ASCII layout sketch showing information hierarchy
4. **Component inventory**: Which existing components to reuse, which to create
5. **Responsive notes**: How the layout adapts at each breakpoint
6. **Interaction notes**: Hover states, click targets, loading states, empty states, error states
7. **Accessibility notes**: Any special ARIA, keyboard, or screen reader considerations

---

## Project Design System Quick Reference

Refer to `/baseline-ui` skill for the complete design system. Key points:

- **Colors**: Navy primary (#1a365d), Red secondary (#e53e3e), Green accent (#38a169)
- **Cards**: `card border-0 shadow-sm` with `card-header bg-white fw-semibold`
- **Tables**: `table-responsive > table table-hover mb-0`, `thead table-light`
- **Badges**: `badge bg-{success|warning|info|secondary|danger}`
- **Buttons**: Always `btn-sm` in admin UI
- **Layout**: `AdminLayout` shell with dark navbar, `bg-light` main, `container py-4`
