mcpField
C
click-test-plan

click-test-plan

github.com/owl-listenerTesting & quality3.1k2.1k installsUpdated 8w ago
Repository

About click-test-plan

A UX research skill for planning click tests that assess findability and navigation clarity. It structures objectives, stimuli, tasks, success criteria, and participant selection, with guidance for analyzing clicks, timing, and confidence.

Key features

  1. 01First-click, click-path, navigation, and five-second tests
  2. 02Objective, stimuli, and task planning
  3. 03Success metrics for clicks and timing
  4. 04Participant criteria and segmentation
  5. 05Analysis of click patterns and confidence

Use cases

  1. 01Testing whether users can find a feature
  2. 02Comparing navigation designs with the same tasks
  3. 03Evaluating first-click success and hesitation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill click-test-plan

After installing, type/click-test-planin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported