SkillAgentSearch skills...

fitts-law

Apply Fitts's Law — target acquisition time depends on size and distance

Install / Use

npx skills add Owl-Listener/designer-skills --skill fitts-law

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Supported Platforms

Zed

Tags

Our assessment of fitts-law

fitts-law scores 80/100 on our quality scale, 3628th of 4,698 Development & Engineering skills we index.

Its SKILL.md is 3.4 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.

With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
12/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so fitts-law is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

fitts-law compared with similar skills

All 4 of these similar skills score higher than fitts-law; compare them before choosing.

SkillScoreStarsUpdatedFormat
fitts-law (this skill)by Owl-Listener802.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install fitts-law?
Run npx skills add Owl-Listener/designer-skills --skill fitts-law. The install tabs above show the steps for each supported agent.
Which AI agents does fitts-law work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is fitts-law safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is fitts-law still maintained?
The repository was last updated about 2 months ago, so fitts-law is actively maintained.

name: fitts-law description: Apply Fitts's Law — target acquisition time depends on size and distance. Use when sizing and positioning controls, especially for touch. For how many controls to show at once, use hicks-law.

Fitts's Law

You are an expert in the relationship between target size, distance, and interaction accuracy.

What You Do

You apply Fitts's Law to ensure interactive targets are sized and positioned to minimize the time and effort required to reach and activate them.

The Principle

The time to acquire a target is a function of distance to the target and target size: MT = a + b × log₂(2D / W) Where: MT = movement time, D = distance to target, W = width of target, a/b = empirically derived constants. In plain terms: large targets close to the pointer are fast to hit; small targets far away are slow and error-prone. Both dimensions — size and proximity — matter independently.

Practical Implications

Target Size

  • Minimum touch target: 44×44pt (Apple HIG) / 48×48dp (Material Design) for touch interfaces
  • Pointer targets can be smaller but should still be generous — 24×24px minimum for pointer, more for small or dense UIs
  • Target size is the interactive area, not the visual icon — a 16px icon can have a 44px tap area
  • Increase size for high-frequency or high-consequence actions (primary CTA, destructive confirm)

Target Distance

  • Place related actions near the content they act on — a card action should live on the card, not across the screen
  • Edges and corners of the screen are infinite-size targets (pointer cannot overshoot) — use them for persistent navigation (macOS menu bar, Windows taskbar)
  • On mobile, bottom-of-screen placement reduces reach distance for right-hand thumb use
  • Dialogs with confirmation actions should not require crossing the full screen to reach "OK"

What Fitts's Law Does Not Cover

  • Cognitive cost: it models motor time, not the time to decide what to tap. A perfectly sized, well-positioned button still fails if the label is ambiguous.
  • Touch accuracy vs pointer accuracy: touch has a larger contact zone and is less precise; pointer mechanics differ. The law applies to both but parameters vary.
  • Gesture targets: swipe areas, drag handles, and scroll zones follow the same principles (bigger + closer = faster) but interact with accidental activation risk in ways the basic model doesn't capture.

Common Design Applications

| Pattern | Fitts's Law Application | |---|---| | Primary CTA | Large, high-contrast, positioned in thumb reach zone | | Floating action button | Bottom-right on mobile — close to dominant thumb | | Navigation tabs | Bottom nav on mobile beats top nav for one-handed use | | Modal actions | Buttons near bottom of modal, not scattered | | Form submit | Full-width or prominent button below the last field | | Close button | Large enough hit target; consider bottom dismiss on mobile | | Destructive action | Small and distant to prevent accidental activation |

Best Practices

  • Always test tap target size on real devices — what looks adequate in design tools is often too small in hand
  • Use padding, not visual size, to expand hit targets
  • Do not apply Fitts's Law in isolation to justify oversized buttons; balance with visual hierarchy and spacing
  • On desktop, exploit screen edges for persistent navigation; don't waste them
  • Audit high-error interactions (mis-taps, mis-clicks) first — they are almost always Fitts's Law failures

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryDevelopment
Updated2mo ago
Forks388

Languages

Markdown

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions