본문으로 건너뛰기
cccskills
무료GitHub에 공개

fitts-law

Review button sizes and placement using Fitts's Law, which relates movement time to target size and distance. Plan touch areas and pointer controls that are easier to reach and activate, while considering spacing and accidental taps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Review mobile button sizes and thumb reach
  • Expand tap areas around small icons
  • Place form and dialog actions within easy reach
  • Investigate frequent mistaps and misclicks

포함된 파일(1)

  • SKILL.md3.5 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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Owl-Listener의 스킬 모두 보기

이 스킬의 문제 신고