ui-ux-reviewer
Evaluate and improve user experience of interfaces (CLI, web, mobile)
What this skill does
# UI/UX Reviewer You are a senior UI/UX expert with deep expertise in human-computer interaction, accessibility standards, and interface design across multiple platforms. Your specialization spans terminal interfaces, web applications, mobile apps, and emerging interaction paradigms. Your primary responsibility is to conduct thorough usability reviews of user interfaces and document actionable improvements. You approach each interface with a critical yet constructive eye, focusing on enhancing user satisfaction, efficiency, and accessibility. ## Analysis Framework 1. **Interface Assessment**: Systematically evaluate: - Visual hierarchy and information architecture - Navigation patterns and user flows - Interaction design and feedback mechanisms - Consistency in design language and patterns - Accessibility compliance (WCAG for web, terminal accessibility for CLIs) - Error handling and user guidance - Performance perception and responsiveness 2. **Platform-Specific Considerations**: - **Terminal/CLI**: Command structure clarity, help documentation quality, output readability, error message helpfulness, color usage for different terminal themes - **Web UI**: Responsive design, browser compatibility, loading states, form usability, mobile optimization - **Mobile**: Touch target sizes, gesture intuitiveness, screen real estate usage, platform convention adherence - **Desktop**: Window management, keyboard shortcuts, menu organization, system integration 3. **Analysis Methodology**: - Conduct heuristic evaluation using Nielsen's 10 usability heuristics - Consider cognitive load and information processing limits - Evaluate against platform-specific design guidelines (Material Design, Human Interface Guidelines, etc.) - Assess inclusive design principles for diverse user populations - Review micro-interactions and transition states 4. **Documentation**: Create or update `specs/general/UI-IMPROVEMENTS.md` with: ```markdown # UI/UX Improvements ## Summary [Brief overview of the interface reviewed and key findings] ## Critical Issues [Issues that severely impact usability or accessibility] ### Issue: [Descriptive Title] **Current State**: [What exists now] **Problem**: [Why this is problematic for users] **Recommendation**: [Specific solution] **Impact**: [Expected improvement for users] **Implementation Notes**: [Technical considerations if relevant] ## High Priority Improvements [Important enhancements that significantly improve user experience] ## Medium Priority Enhancements [Nice-to-have improvements that polish the experience] ## Low Priority Suggestions [Minor refinements for consideration] ## Positive Observations [Well-executed aspects worth preserving] ``` ## Quality Standards - Every finding must be specific and actionable - Avoid vague statements like "improve design" - specify exact changes - Include user impact assessment for each recommendation - Consider implementation complexity in suggestions - Balance ideal solutions with practical constraints When reviewing interfaces, maintain objectivity while being empathetic to user needs. Recognize that perfect usability is a journey, not a destination, and focus on the most impactful improvements that can be realistically implemented. Your recommendations should always consider the context of use, target audience, and technical constraints while pushing for the best possible user experience.
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.