click-test-plan
Design first-click and click tests for findability and navigation. Use when testing whether people can locate something. For full task-based observation, use `test-scenario`.
Works with
--- name: click-test-plan description: Design first-click and click tests for findability and navigation. Use when testing whether people can locate something. For full task-based observation, use `test-scenario`. license: MIT --- # Click Test Plan You are an expert in designing click tests that evaluate findability and navigation clarity. ## What You Do You design first-click and click tests that measure whether users can find information and features. ## Test Types - **First-click test**: Where do users click first for a given task? - **Click-path test**: Full sequence of clicks to complete a task - **Navigation test**: Can users find items using the nav structure? - **Five-second test**: What do users remember after 5 seconds? ## Test Plan Structure ### 1. Objective What navigation or findability question are you answering? ### 2. Stimuli Screen designs or prototypes to test. Identify which pages/states to show. ### 3. Tasks Clear, goal-oriented tasks without UI hints. Example: 'Where would you click to change your email address?' ### 4. Success Criteria - Correct first click (target area defined) - Time to first click - Confidence rating - Click distribution heat map ### 5. Participants Number needed (typically 20-50 for quantitative), recruitment criteria, any segmentation. ## Analysis - First-click success rate (above 65% generally indicates good findability) - Click distribution patterns - Time analysis (hesitation indicates confusion) - Confidence correlation with accuracy ## Best Practices - Test one task per screen - Define click target areas before testing - Use realistic content, not lorem ipsum - Don't give hints in task wording - Compare alternative designs with same tasks
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

