generic-ux-designer
Professional UX expertise for any project type. Covers user research, design thinking, interaction patterns, accessibility, and design critique. Use when designing new features, improving UX, conducting design reviews, or evaluating user flows. For visual UI work, combine with ui-research skill.
What this skill does
# Generic UX Designer Professional UX expertise adapting to any project's constraints. ## Combine with Research for Visual Work For UI/visual design decisions, also use: ``` Skill(ui-research) # Research inspiration first ``` **References:** - [UX Principles](../_shared/UX_PRINCIPLES.md) - UX methodology - [UI Inspiration Sources](../_shared/UI_INSPIRATION_SOURCES.md) - Visual research ## When to Use This Skill **Use for:** - Designing new features or flows - Improving existing user experience - Conducting design reviews/critiques - Evaluating user flows and interactions - Making accessibility decisions - Choosing between design alternatives **Don't use when:** - Visual styling/tokens → use `generic-design-system` - Code architecture → use `generic-feature-developer` - Code quality review → use `generic-code-reviewer` ## Design Thinking Process 1. **Empathize** - Understand user needs, pain points, journeys 2. **Define** - Problem statements, personas, success metrics 3. **Ideate** - Brainstorm solutions, explore alternatives 4. **Prototype** - Low-fidelity first, test assumptions 5. **Test** - Usability testing, iterate on data ## Research Decision Guide ### When to Research vs Ship | Situation | Action | | -------------------- | ------------------------------------ | | New product/feature | Full research (interviews + testing) | | Incremental change | Quick critique (heuristic review) | | Bug fix | No research needed | | A/B decision | Analytics + small test | | Controversial design | Stakeholder alignment first | ### Method Selection - Need user motivation? → Interviews - Need usability feedback? → Testing - Need quick quality check? → Heuristic evaluation - Need quantitative data? → Surveys/Analytics - Have no users yet? → Competitor analysis + proto-personas ### Research Scope by Confidence | Confidence Level | Action | | -------------------------- | -------------- | | High (established pattern) | Skip research | | Medium (some uncertainty) | Quick critique | | Low (new territory) | Full research | **Reference:** See UX_PRINCIPLES.md for detailed method frameworks ## User Psychology Applied ### Cognitive Load - Reduce choices (Hick's Law) - Chunk information (Miller's Law) - Progressive disclosure - Minimize memory load ### Visual Hierarchy - Size indicates importance - Contrast draws attention - Whitespace groups elements - F-pattern/Z-pattern reading ## Interaction Patterns ### Navigation | Pattern | Use Case | | ---------- | --------------------------- | | Top nav | Simple sites, < 7 items | | Side nav | Complex apps, many sections | | Bottom nav | Mobile apps, < 5 items | | Tabs | Related content sections | ### Forms - Single column layout - Inline validation - Smart defaults - Progress indicators ### Feedback | Pattern | Use Case | | -------- | ------------------- | | Toast | Non-blocking info | | Modal | Blocking/important | | Inline | Contextual feedback | | Skeleton | Loading states | ## Mobile Considerations - Touch targets: 44x44px minimum - 8px spacing between targets - Thumb-friendly placement - Bottom sheets for actions ## Accessibility (UX Perspective) | Aspect | Approach | | --------- | -------------------------------- | | Vision | High contrast, scalable text | | Motor | Large targets, keyboard nav | | Cognitive | Simple language, clear structure | | Hearing | Captions, visual indicators | ## Heuristic Evaluation in Practice ### Quick Scan (5 minutes) | Heuristic | Quick Check | | ---------------- | ------------------------------------ | | Visibility | Is current state obvious? | | Feedback | Does every action have response? | | Consistency | Do similar things look/work similar? | | Error Prevention | Can user easily make mistakes? | | Recovery | Can user undo/fix errors? | ### Common Violations to Flag - Hidden system state (loading with no indicator) - Silent failures (action with no feedback) - Inconsistent patterns (different buttons for same action) - Destructive without confirm (delete with no undo) - Jargon in user-facing text ### Presenting Findings ``` Issue: [What's wrong] Heuristic: [Which violated] Impact: [User consequence] Suggestion: [How to fix] Priority: P0/P1/P2 ``` ## Design Critique Framework | Aspect | Questions | | ------------- | ----------------------------- | | Usability | Can users complete tasks? | | Clarity | Is purpose immediately clear? | | Consistency | Follows established patterns? | | Hierarchy | Most important stands out? | | Feedback | Users know system state? | | Accessibility | Works for everyone? | ## UX Patterns ### Empty States 1. Explain what goes here 2. Guide to first action 3. Show example content ### Loading States 1. Skeleton screens > spinners 2. Progress for long operations 3. Optimistic UI when safe ### Error States 1. Explain what happened 2. Suggest how to fix 3. Don't blame user ## UX Output Checklist Before presenting UX recommendation: - [ ] User problem clearly defined - [ ] Solution addresses root cause (not symptom) - [ ] Accessibility considered - [ ] Edge cases identified - [ ] Implementation complexity noted - [ ] Success metrics defined ## Design Review Checklist - [ ] Primary task achievable - [ ] Clear visual hierarchy - [ ] Keyboard navigable - [ ] Touch targets sized - [ ] Copy clear and helpful ## See Also - [UX Principles](./../_shared/UX_PRINCIPLES.md) - Research methods, heuristics, psychology - [Design Patterns](./../_shared/DESIGN_PATTERNS.md) - Visual patterns and components - `generic-design-system` - For tokens, styling, visual consistency - `generic-feature-developer` - For implementation architecture - Project `CLAUDE.md` - Project-specific constraints **READ UX_PRINCIPLES.md for:** - Full research method frameworks → methods section - Complete Nielsen heuristics → evaluation section - Quick critique workflow → critique section
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.