本文へ移動
cccskills
無料GitHub で公開

fitts-law

Apply Fitts's Law to size and position interactive targets for fast, accurate interaction.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

PatternFitts's Law Application
Primary CTALarge, high-contrast, positioned in thumb reach zone
Floating action buttonBottom-right on mobile — close to dominant thumb
Navigation tabsBottom nav on mobile beats top nav for one-handed use
Modal actionsButtons near bottom of modal, not scattered
Form submitFull-width or prominent button below the last field
Close buttonLarge enough hit target; consider bottom dismiss on mobile
Destructive actionSmall 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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

Format CVs for academic positions with publications, grants, and teaching

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

Create accessibility testing plans covering assistive technologies and WCAG criteria.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

日本語の概要は準備中です。原文の説明を表示しています。

Infrasity-Labs/dev-gtm-claude-skills1362026年6月29日 更新

Infrasity-Labs のスキルをすべて見る

このスキルの問題を報告する