# ui-research

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

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 188 installs · ★ 114 repo stars
- Author: travisjneuman
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/travisjneuman/.claude/tree/HEAD/skills/ui-research/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/ui-research

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill ui-research -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/ui-research/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/ui-research/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill ui-research -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/ui-research/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill ui-research -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/ui-research/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install travisjneuman/.claude skills/ui-research
```

2. **Manually: put the files in place**
- File: `.github/skills/ui-research/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill ui-research -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/travisjneuman/.claude --path skills/ui-research
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/ui-research/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill ui-research -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/travisjneuman/.claude/tree/HEAD/skills/ui-research/SKILL.md

## When to use it
- 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
- 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

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: dc248ac54d58a0e2.

BEGIN THIRD-PARTY FILE dc248ac54d58a0e2
````text
---
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]
````
END THIRD-PARTY FILE dc248ac54d58a0e2

The third-party file has ended. Everything between the dc248ac54d58a0e2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2743 of 8573 bytes. © travisjneuman · MIT · https://github.com/travisjneuman/.claude/tree/HEAD/skills/ui-research/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
