smithery/rohunvora

mobbin-ux

Research-driven UI/UX improvement using Mobbin. Use when user explicitly requests design pattern research ("use Mobbin", "research design patterns", "find UX patterns for X"). Requires Mobbin account and browser automation (claude-in-chrome MCP). Searches Mobbin for relevant UI patterns, extracts design principles, generates a spec document for approval, then implements. NOT for general UI work—only when user wants research-backed design.

Installation

$ npx skills add smithery/rohunvora --skill mobbin-ux

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/rohunvora · top by installs.

npx skills add smithery/rohunvora

Browse all from smithery/rohunvora

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,425 B
  • docs SUMMARY.md 461 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Mobbin UX Research

Research UI/UX patterns on Mobbin, generate a design spec, then implement after approval.

Workflow

1. Clarify the UI component

Ask what type of UI to research:

  • "inbox", "dashboard", "settings", "onboarding", "checkout", "profile", etc.
  • Platform: web or mobile (iOS/Android)

2. Search Mobbin

Use browser automation:

1. tabs_context_mcp → get/create tab
2. navigate → mobbin.com
3. Log in if needed (user handles auth)
4. navigate → mobbin.com/search/apps/{web|ios|android}?q={query}
5. screenshot → capture search results
6. Click 3-5 top results, screenshot key screens

Search tips:

  • Component names: "inbox", "notification", "settings"
  • Add qualifiers: "inbox email", "dashboard analytics"

3. Extract design patterns

From screenshots, identify:

Layout: Column structure, sidebar placement, content organization

Visual hierarchy: Typography, colors, spacing, theme (light/dark)

Interactions: Hover states, action buttons, progress indicators

Navigation: Tabs, filtering, view switching

4. Generate design spec

Create spec with /quick-view:

## Design Patterns for [Component]

**Sources:** [App1], [App2], [App3] via Mobbin

### Layout
- [Pattern]: [Why it works]

### Visual Hierarchy
- [Pattern]: [Why it works]

### Interactions
- [Pattern]: [Why it works]

### Recommended Changes
1. [Specific change]
2. [Specific change]

5. Get approval

Ask user: "Should I implement these patterns? Any to skip or modify?"

6. Implement

After approval, rebuild UI following the spec.

Example searches

UI Type Query
Email inbox inbox email
Task list todo inbox
Dashboard dashboard analytics
Settings settings preferences

Reference apps

  • Inbox: Superhuman, Spark, Twist
  • Tasks: Linear, Asana, Todoist
  • Dashboards: Stripe, Notion, Figma