Skip to main content
skill CX Codex

ui-research — Claude Code skill: gathering real UI references

ui-research — a research-first interface workflow that guides agents to study real shipped products, gather proven UI patterns, and prevent generic AI styling.

MIT 188 installs ★ 114 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add travisjneuman/.claude --skill ui-research -a claude-code
Open on GitHub

What ui-research does

The skill introduces a five-phase research cycle before writing any frontend code: Define, Research, Collect, Analyze, and Design Brief. Instead of generating boilerplate UI right away, the agent identifies constraints, selects reference interfaces from platforms like Mobbin, Land-book, or Godly, and extracts reusable structural patterns.

It enforces a catalog of generic AI design red flags to avoid, including default purple gradients, overused glassmorphism, unDraw-style graphics, and pill-shaped buttons on every element. The workflow requires inspecting at least three real shipped products before settling on typography, layouts, and component libraries such as shadcn/ui.

If the agent lacks web browsing capabilities in your session, you will need to paste research URLs and screenshots directly into the prompt.

What it helps with

  • collect real-world UI references before coding visual components
  • eliminate synthetic design tropes such as purple gradients and identical card grids
  • compile a structured design brief covering layout, fonts, and animation choices
  • select platform-appropriate UX patterns for web dashboards or mobile screens

Example prompts for the agent

  • Run ui-research for our fintech analytics dashboard before coding components
  • Audit our landing page structure against the ui-research anti-pattern checklist
  • Gather mobile checkout flow patterns according to the ui-research workflow

How to install ui-research

1Skills CLI (Vercel)

npx skills add travisjneuman/.claude --skill ui-research -a claude-code

2Manually: put the files in place

~/.claude/skills/ui-research/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ui-research/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ui-research

How to install ui-research in Claude Code?

Run npx skills add travisjneuman/.claude --skill ui-research -a claude-code in your terminal.

What is the goal of the ui-research skill?

It grounds frontend development in real, working digital products rather than speculative AI concepts. This prevents generic layouts and ensures coherent interface decisions.

What design anti-patterns does the skill flag?

The guide explicitly warns against purple gradients, unDraw illustrations, monospace eyebrow labels, default cream backgrounds, and repetitive pill-shaped buttons.

Source text

SKILL.md · MIT
---
name: ui-research
description: Research-first UI/UX design workflow. Use BEFORE any frontend visual work to research modern patterns, gather inspiration from real products, and avoid generic AI-generated looks. Mandatory prerequisite for quality UI work.
---

# UI Research

Research real products before designing new UI, so the result is grounded in how shipped products solve the problem.

This skill ensures UI work is informed by real-world inspiration, modern patterns, and human-centered design - not generic AI output.

**Essential Reference:** See [UI Inspiration Sources](../_shared/UI_INSPIRATION_SOURCES.md)

---

## When to Use This Skill

Use before:

- Creating new UI components
- Designing landing pages
- Building dashboards or admin UIs
- Developing mobile app screens
- Any visual/frontend work

---

## Research Workflow

### Phase 1: Define

Before searching, answer:

```
1. What am I building? (component, page, flow)
2. What platform? (web, iOS, Android, desktop)
3. What industry? (SaaS, e-commerce, fintech, etc.)
4. What feeling? (professional, playful, minimal, bold)
5. What constraints? (existing brand, tech stack, timeline)
```

### Phase 2: Research

**Search Strategy:**

```bash
# For each UI task, search at least 3 sources:

# 1. Real products (MOST IMPORTANT)
Search: Mobbin, UI Sources, Refero
Why: See how real companies solved this problem

# 2. Curated galleries
Search: Land-book, Awwwards, Godly
Why: High-quality, vetted designs

# 3. Component patterns
Search: shadcn/ui, Collect UI, Dribbble
Why: Specific UI element inspiration
```

**Search Queries by Task:**

| Building     | Search Terms                                              |
| ------------ | --------------------------------------------------------- |
| Dashboard    | "analytics dashboard", "admin panel", "SaaS dashboard"    |
| Landing page | "[industry] landing page", "hero section", "pricing page" |
| Mobile app   | "[app type] iOS", "mobile [feature]", "[competitor] app"  |
| E-commerce   | "product page", "checkout flow", "cart design"            |
| Auth flows   | "login screen", "onboarding", "signup form"               |
| Settings     | "settings page", "profile settings", "preferences"        |

### Phase 3: Collect

Save 5-10 examples that resonate. For each, note:

```
URL/Source: [where you found it]
What works: [specific elements you like]
Patterns: [repeating solutions across examples]
Unique: [what makes this stand out]
Adapt: [how to apply to our project]
```

### Phase 4: Analyze

**Pattern Recognition:**

```
Common patterns across examples:
- Layout: [grid, spacing, hierarchy]
- Colors: [palette trends, contrast]
- Typography: [fonts, scale, weights]
- Components: [buttons, cards, forms]
- Interactions: [hover, transitions, feedback]
```

**Quality Checklist:**

- [ ] Found 3+ real shipped products (not concepts)
- [ ] Identified repeating patterns
- [ ] Noted unique differentiators
- [ ] Considered accessibility
- [ ] Checked mobile responsiveness

### Phase 5: Design Brief

Before implementing, document:

```markdown
## UI Research Brief

### Inspiration Sources

- [Link 1]: [What to adopt]
- [Link 2]: [What to adopt]
- [Link 3]: [What to adopt]

### Key Patterns to Follow

- Layout: [specific approach]
- Color: [palette direction]
- Typography: [font choices]
- Components: [style decisions]

### Differentiation

- [What makes ours unique]
- [Brand personality elements]

### Technical Approach

- Component library: [shadcn/ui, etc.]
- Animation approach: [Framer Motion, CSS]
- Responsive strategy: [mobile-first, etc.]
```

---

## Source Selection Guide

### By Project Type

| Project          | Primary Sources         | Secondary               |
| ---------------- | ----------------------- | ----------------------- |
| **SaaS App**     | Mobbin, UI Sources      | Land-book, shadcn/ui    |
| **Landing Page** | Land-book, Godly        | Awwwards, One Page Love |
| **Mobile App**   | Mobbin, Screenlane      | Pttrns, Apple HIG       |
| **E-commerce**   | Baymard, Awwwards       | Mobbin, UI Sources      |
| **Dashboard**    | Dribbble, UI Sources    | Ant Design, Tremor      |
| **Portfolio**    | Awwwards, One Page Love | Godly, personal sites   |

### By Platform

| Platform           | Required Research                    |
| ------------------ | ------------------------------------ |
| **iOS**            | Apple HIG, Mobbin (iOS filter)       |
| **Android**        | Material 3, Mobbin (Android filter)  |
| **Web**            | Awwwards, Land-book, shadcn/ui       |
| **Desktop**        | Fluent 2, platform-specific apps     |
| **Cross-platform** | All of the above, find common ground |

---

## Avoiding the "AI Look"

### Red Flags to Avoid

```
GENERIC AI PATTERNS (Don't do these):
- Blue/purple gradient backgrounds
- Perfectly symmetrical everything
- Generic blob/wave decorations
- Undraw-style illustrations
- "Hero with laptop mockup" layouts
- Default color schemes unchanged
- Cookie-cutter card grids
- Overused glassmorphism
- Cream/off-white page background by default
- Italic accent words inside headlines
- Numbered "01 / 02 / 03" section labels
- Monospace eyebrow labels
- Pill-shaped buttons everywhere
```

### Human Touch Elements

```
WHAT MAKES DESIGN FEEL HUMAN:
- Custom color palette with personality
- Intentional asymmetry
- Unique typography combinations
- Real photography or custom illustration
- Micro-interactions with character
- Subtle organic shapes
- Brand-specific details
- Thoughtful empty states
- Personality in copywriting
```

### Quality Signals

| Aspect        | Generic AI     | Human-Polished                   |
| ------------- | -------------- | -------------------------------- |
| **Color**     | Default blue   | Custom brand palette             |
| **Layout**    | Perfect grid   | Intentional variation            |
| **Images**    | Stock photos   | Custom/curated imagery           |
| **Copy**      | Lorem ipsum    | Real, personality-rich text      |
| **Animation** | Standard fades | Purposeful, branded motion       |
| **Details**   | None           | Hover states, micro-interactions |

---

## Research Tools

### Browser Extensions

- **Muzli** - Design inspiration feed
- **Panda** - News and inspiration dashboard
- **Stylify Me** - Extract site colors/fonts

### Screenshot Tools

- **Full Page Screen Capture** - Capture entire pages
- **Awesome Screenshot** - Annotate and save

### Organization

- **Figma** - Create mood boards
- **Notion** - Document research
- **Eagle** - Visual bookmark manager
- **Pinterest** - Quick collection

---

## Research Output Template

```markdown
# UI Research: [Component/Page Name]

## Context

- **Building:** [what]
- **Platform:** [where]
- **Constraints:** [limitations]

## Inspiration (5-10 sources)

### 1. [Company/Site Name]

- **URL:** [link]
- **Screenshot:** [attached]
- **What works:** [specific elements]
- **Adopt:** [what to use]

### 2. [Company/Site Name]

...

## Pattern Analysis

### Layout

- [Common layout patterns observed]

### Color

- [Palette trends]

### Typography

- [Font and scale patterns]

### Components

- [UI element patterns]

## Design Direction

### Must Have

- [Non-negotiable elements]

### Nice to Have

- [Enhancement opportunities]

### Avoid

- [Anti-patterns to skip]

## Technical Stack

- **Components:** [library choice]
- **Styling:** [approach]
- **Animation:** [library/method]
```

---

## Integration with Other Skills

After research, proceed to:

| Next Step             | Skill to Use            |
| --------------------- | ----------------------- |
| Visual implementation | `frontend-enhancer`     |
| Design system setup   | `generic-design-system` |
| UX flow design        | `generic-ux-designer`   |
| Animation work        | `ui-animation`          |
| Brand alignment       | `brand-identity`        |

---

## Quick Start Checklist

Before ANY UI work:

- [ ] Defined what I'm building
- [ ] Searched 3+ inspiration sources
- [ ] Collected 5+ relevant examples
- [ ] Identified repeating patterns
- [ ] Noted unique differentiators
- [ ] Created brief design direction
- [ ] Checked for "AI look" red flags
- [ ] Planned human touch elements

---

## See Also

- [UI Inspiration Sources](../_shared/UI_INSPIRATION_SOURCES.md) - Full source list with URLs
- [Design Patterns](../_shared/DESIGN_PATTERNS.md) - Visual design tokens
- `frontend-enhancer` - For implementation after research
- `generic-design-system` - For design system work
- `graphic-design` - For visual design principles

© travisjneuman · MIT · travisjneuman/.claude

Similar skills

All skills for Design →

From the same set117

The whole set →
tauri-desktop The tauri-desktop skill guides Tauri 2.0 app setup, from Rust commands and frontend IPC to permissions and builds. Use it when planning desktop or mobile apps. CX Codex +1 195installs monetization-strategy The monetization-strategy Claude Code skill helps choose revenue models and shape pricing for products and services. It is activated for pricing strategy, business model selection, and revenue planning. CX Codex +1 194installs generic-react-design-system generic-react-design-system is a Claude Code skill that provides reference patterns for React and TypeScript interfaces with Tailwind CSS, Framer Motion, and WCAG AA. CX Codex +1 191installs data-science Data science guidance covering machine learning pipelines, statistics, and business intelligence. Helps configure models, data governance, and dashboards. CX Codex +1 189installs research-presenter research-presenter — a Claude Code skill that turns research findings into presentation outlines with narrative structure and data visualization advice. Runs when preparing conference talks or briefings. CX Codex +1 188installs ios-development ios-development — a skill for Claude Code guides native app creation across iOS, iPadOS, tvOS, and watchOS using Swift. Activates when structuring views, configuring async workflows, or matching Apple design rules. CX Codex +1 186installs volunteer-coordinator The volunteer-coordinator skill structures volunteer programs with role definitions, scheduling, skill matching, and communication planning. Use it when setting up or revising volunteer coordination. CX Codex +1 184installs recipe-card-creator The recipe-card-creator skill turns recipe details into structured cards, adjusts quantities for serving counts, and supports meal plans, shopping lists, and collections. CX Codex +1 183installs

Project sponsors

Companies that keep this analytics open