원클릭으로 Manus에서 모든 스킬 실행

$pwd:

mobbin-ux

Name: Mobbin Ux
Author: rohunvora

// 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.

Manus에서 실행

$ git log --oneline --stat

stars:20

forks:1

updated:2026년 1월 7일 00:55

SKILL.md

readonly

name

mobbin-ux

description

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.

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

related-skills.json

같은 저장소

webhook-notify.md

from "rohunvora/cool-claude-skills"

Set up webhook-to-desktop notification systems using Cloudflare Workers and ntfy.sh. Use when users want to receive desktop notifications for webhooks from services like Stripe payments, GitHub events, custom app alerts, error monitoring, or any webhook source. Handles the full setup including worker deployment, local listener, and background service installation. Supports custom sounds, click actions, rich content, and event filtering.

2026-01-0920

ai-loading-ux.md

from "rohunvora/cool-claude-skills"

Design AI loading, thinking, and progress indicator UX. Use when explicitly asked to improve AI waiting states, add thinking indicators, or design loading UX for AI interfaces. Covers reasoning display (chain-of-thought), progress steps, streaming states, and the "elevator mirror effect" for reducing perceived wait time.

2026-01-0420

imsg-ingest.md

from "rohunvora/cool-claude-skills"

Primary iMessage interface. Full-featured CLI for message export, conversation management, contact resolution, and thread state. Use when user mentions "imessage", "imsg", "text message", "iphone messages", or phone numbers. Triggers: "imessage messages", "export imessage", "text from john", "imessage contacts", "sync imessage". This is STANDALONE - do not defer to unified-messages for iMessage operations.

2026-01-0220

tg-ingest.md

from "rohunvora/cool-claude-skills"

Primary Telegram interface. Full-featured CLI for message export, DM management, group sync, contact scoring, and thread state. Use when user mentions "telegram", "tg", "@username", or telegram-specific terms. Triggers: "telegram messages", "export telegram", "telegram DMs", "telegram groups", "sync telegram", "@username messages", "telegram contacts". This is STANDALONE - do not defer to unified-messages for telegram operations.

2026-01-0220

unified-messages.md

from "rohunvora/cool-claude-skills"

Cross-platform messaging aggregator. Use as DEFAULT when user does NOT specify a platform (telegram/imessage). Provides unified inbox, search, and triage across both platforms. Triggers: "check messages" (no platform), "inbox", "who messaged me", "all my messages", "triage". NOT for platform- specific requests - use tg-ingest for "telegram X" or imsg-ingest for "imessage X".

2026-01-0220

skill-creator.md

from "rohunvora/cool-claude-skills"

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

2026-01-0220

package.json

"author": "rohunvora"

"repository": "rohunvora/cool-claude-skills"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

그래픽 디자이너예술, 디자인, 엔터테인먼트, 스포츠, 미디어직27-1024L4

실내 디자이너L4

name

mobbin-ux

description

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

mobbin-ux

Mobbin UX Research

Workflow

1. Clarify the UI component

2. Search Mobbin

3. Extract design patterns

4. Generate design spec

5. Get approval

6. Implement

Example searches

Reference apps

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Mobbin UX Research

Workflow

1. Clarify the UI component

2. Search Mobbin

3. Extract design patterns

4. Generate design spec

5. Get approval

6. Implement

Example searches

Reference apps