usability-tester
Conduct usability tests and identify UX issues through systematic observation. Use when testing user flows, validating designs, identifying friction points, running heuristic evaluations, or ensuring users can complete core tasks. Use for test planning, think-aloud protocol, task scenarios, severity rating, accessibility evaluation.
What this skill does
# Usability Tester ## Overview Validates that users can successfully complete core tasks through systematic observation and expert evaluation. Covers moderated and unmoderated testing, heuristic evaluation, accessibility checks, and issue severity scoring. Not a substitute for analytics or A/B testing -- those measure what happens, usability testing reveals why. **When to use:** Testing user flows, validating designs, identifying friction points, running heuristic evaluations, ensuring users can complete core tasks, planning and executing usability test sessions. **When NOT to use:** Analytics or A/B test setup, visual design critique without task-based evaluation, automated UI testing (use a testing framework), performance benchmarking. ## Quick Reference | Method | Best For | Participants | When to Use | | ---------------------- | --------------------------------------- | --------------------------- | -------------------------------------- | | Moderated testing | Deep insights, complex flows | 5-8 per persona | Design and prototyping stage | | Unmoderated testing | Scale, quantitative data | 20-50+ | Pre-launch and post-launch | | Guerrilla testing | Quick validation, early concepts | 5-10 random | Early concept stage | | First-click testing | Navigation, information architecture | 20-50 | Any stage, especially IA redesigns | | Heuristic evaluation | Expert review against principles | 3-5 evaluators | Before user testing, design audits | | Cognitive walkthrough | Task flow analysis | 2-3 evaluators | Early design, new feature review | | Accessibility audit | Inclusive design validation | 3-5 users with disabilities | Pre-launch, compliance reviews | | Synthetic user testing | Scalable task validation with AI agents | N/A (automated) | Continuous, regression testing | | AI-moderated sessions | Async moderated testing at scale | 10-50+ | When moderator availability is limited | ## Core Metrics | Metric | Target | What It Measures | | ---------------------- | ------------------------------------------- | --------------------------- | | Task success rate | 80% or higher for core tasks | Can users complete the task | | Time on task | Simple under 30s, medium 1-2m, complex 3-5m | Efficiency | | Error rate | Fewer than 2 per task | Learnability and clarity | | Post-task satisfaction | 4.0 or higher on 5-point scale | Subjective ease | | SUS score | 68+ (industry average), 80+ (excellent) | Overall usability | ## Issue Severity Severity equals Impact (1-3) multiplied by Frequency (1-3). Critical (8-9): fix before release. High (6-7): fix before release. Medium (4-5): next release. Low (1-3): backlog. ## Common Mistakes | Mistake | Correct Pattern | | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | Writing task scenarios with product jargon or step-by-step instructions | Use natural language with realistic context and clear goals to test discoverability | | Helping users or explaining the UI during test sessions | Observe silently and let users struggle; confusion reveals real issues | | Testing only the happy path with ideal inputs | Include error states, edge cases, and recovery scenarios in test plans | | Using fewer than 5 participants per persona | Recruit 5-8 users per persona; after 5, diminishing returns per Nielsen research | | Collecting findings without severity scoring or follow-up actions | Score every issue by impact times frequency and assign fix priority | | Skipping heuristic evaluation before user testing | Run expert review first to catch obvious issues cheaply before spending on recruitment | | Ignoring accessibility in test planning | Include participants with disabilities and test with assistive technologies | | Running only one round of testing | Test in waves: 5 users, fix issues, test 5 more until success rate meets targets | ## Delegation - **Test plan and scenario creation**: Use `Task` agent to draft objectives, research questions, and realistic task scenarios for each persona - **Heuristic evaluation**: Use `Task` agent to walk through interfaces against Nielsen's 10 heuristics and document violations with severity ratings - **Metrics analysis and severity scoring**: Use `Task` agent to calculate SUS scores, task success rates, and severity ratings from raw test data - **Test report generation**: Use `Task` agent to compile findings into structured reports with prioritized recommendations - **Test infrastructure planning**: Use `Plan` agent to select testing methods, define recruitment criteria, and schedule test waves > If the `quality-auditor` skill is available, delegate full codebase quality audits and scoring to it. > Otherwise, recommend: `pnpm dlx skills add oakoss/agent-skills -s quality-auditor -a claude-code -y` ## References - [Test Planning](references/test-planning.md) -- objectives, research questions, recruitment, task scenario templates, screening criteria - [Conducting Tests](references/conducting-tests.md) -- think-aloud protocol, facilitation rules, post-task questions, session structure - [Testing Methods](references/testing-methods.md) -- unmoderated, guerrilla, first-click, cognitive walkthrough, method selection by lifecycle stage - [Heuristic Evaluation](references/heuristic-evaluation.md) -- Nielsen's 10 heuristics, evaluation process, severity rating, combining with user testing - [Metrics and Severity](references/metrics-severity.md) -- success rate, time on task, errors, satisfaction, SUS scoring, severity formula - [Reporting](references/reporting.md) -- test report template, key insights format, stakeholder presentation, recommended actions - [Accessibility Testing](references/accessibility-testing.md) -- inclusive recruitment, assistive technology testing, WCAG alignment, accessibility heuristics - [Remote and Tools](references/remote-and-tools.md) -- remote vs in-person comparison, testing tools, test frequency, checklists
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.