ui-research
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.
What this skill does
# UI Research **Research before you design. Every time.** 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 **ALWAYS use before:** - Creating new UI components - Designing landing pages - Building dashboards or admin UIs - Developing mobile app screens - Any visual/frontend work **This skill is MANDATORY for quality UI work.** --- ## Research Workflow ### Phase 1: Define (5 min) 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 (15-30 min) **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 (10 min) 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 (10 min) **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 (5 min) 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 ``` ### 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 -
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.