Skip to content
Design
Skill

/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`.

BOOST
From plugin
designer-skills
2.9k111 skills33 commands
Install
$ npx -y skills add Owl-Listener/designer-skills --skill click-test-plan --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/click-test-plan

Context preview

The summary Claude sees to decide when to auto-load this skill.

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`.

SKILL.md

click-test-plan.SKILL.md
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`.

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
Read more
Ships withdesigner-skills

Design skills for the agent era, written so an AI agent can actually use them. 273 skills and 76 commands across 33 plugins, in five collections, for Claude Code and Gemini CLI. Not sure which skill you need?

Get the whole plugin

Other skills on designer-skills.