[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JW7YFP4CXBTC98940B2E6J":3,"skill-same:01M6JW7YFP4CXBTC98940B2E6J":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6JW7YFP4CXBTC98940B2E6J","fitts-law-touch-targets",null,"Use this skill when designing for touch — phones, tablets, kiosks, in-car displays, smart-TV remotes, anything where the input is a finger or thumb rather than a precise pointer. Trigger when sizing buttons for mobile, debugging \"users keep mistapping,\" designing a mobile bottom-nav, picking icon sizes for a phone toolbar, or reviewing whether a desktop UI is touch-friendly. Sub-aspect of `fitts-law`; read that first if you haven't already.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Ffitts-law-touch-targets\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"fitts law","fitts law touch targets","targets","touch","icon","buttons","when","for","tv","you","keep","debugging","users","input","trigger","phone","mobile","use","read","first","ui","desktop","2026-11-10 10:12:30",false,"---\nname: fitts-law-touch-targets\ndescription: 'Use this skill when designing for touch — phones, tablets, kiosks, in-car displays, smart-TV remotes, anything where the input is a finger or thumb rather than a precise pointer. Trigger when sizing buttons for mobile, debugging \"users keep mistapping,\" designing a mobile bottom-nav, picking icon sizes for a phone toolbar, or reviewing whether a desktop UI is touch-friendly. Sub-aspect of `fitts-law`; read that first if you haven''t already.'\n---\n\n# Fitts's Law for touch targets\n\nThe finger is a much wider, much less precise pointer than a mouse cursor. Fitts's Law still applies, but the constants change dramatically — and a few touch-specific phenomena (occlusion, thumb reach, edge gestures) layer on top. This skill covers the practical rules.\n\n## Minimum sizes\n\nEvery major touch platform publishes a recommended minimum. They converge:\n\n| Platform \u002F spec | Minimum target | Notes |\n|---|---|---|\n| **Apple HIG (iOS)** | 44×44 pt | The most-cited number; matches average finger contact. |\n| **Material Design (Android)** | 48×48 dp | Roughly equivalent to Apple's 44pt at common densities. |\n| **Microsoft (Windows touch)** | 40×40 effective px | Slightly smaller; Microsoft's research basis. |\n| **WCAG 2.5.5 (Level AAA)** | 44×44 CSS px | Strictest accessibility minimum. |\n| **WCAG 2.5.8 (Level AA, 2.2)** | 24×24 CSS px (with adequate spacing) | Newer, more lenient minimum. |\n\nThe practical rule: **44×44 CSS pixels for any touchable element**. This is the safe number across platforms and accessibility levels. Going smaller is occasionally defensible in specific dense expert contexts; never as a default.\n\nThe visible *icon* inside the button can be smaller (16–24px is common). The *hit area* — the actual touchable region — is what 44×44 measures.\n\n```css\n\u002F* Right: a small icon with a generous tap area *\u002F\n.icon-button {\n  display: inline-grid;\n  place-items: center;\n  width: 44px;\n  height: 44px;\n  padding: 10px;        \u002F* keeps icon centered while tap area stays at 44 *\u002F\n  border: 0;\n  background: transparent;\n  border-radius: 22px;\n}\n.icon-button svg { width: 20px; height: 20px; }\n```\n\n## Spacing between targets\n\nFitts's Law is about acquiring *one* target. When targets are clustered, *spacing* between them prevents accidental neighbor-taps. The convention:\n\n- **At least 8px of clear space** between adjacent touch targets.\n- **44×44 hit area applies to each target**, even if visually they overlap (e.g., padded buttons share visual edges).\n\nFor dense clusters (chip rows, segmented controls), increase visual differentiation: bordered, with internal padding, with adequate gap.\n\n## The thumb-reach map\n\nWhen a phone is held one-handed, the thumb can reach some screen regions easily and others only with strain. Research (Hoober and others) maps this:\n\n```\n+--------------------+\n|       hard         |  \u003C- top of screen, far from thumb base\n|   hard | medium    |\n| medium | easy      |\n| medium | easy      |\n| medium | easy      |  \u003C- bottom-right (right hand) is easiest\n+--------------------+\n```\n\nFor right-handed users, the bottom-right of the screen is easiest; the top-left is hardest. Left-handed users mirror.\n\n**Practical implications:**\n\n- **Primary actions go in the lower portion of the screen.** Floating action buttons (FAB) at bottom-right are a strong Fitts-and-thumb-reach win.\n- **Bottom navigation beats top navigation** for high-frequency tap-to-navigate patterns.\n- **Top-bar actions should be infrequent or hand-agnostic** (search, settings, profile menu — not \"save\" or \"publish\").\n- **Reachability features** (iOS double-tap-home; Android one-handed mode) exist because top corners are genuinely hard.\n\n```html\n\u003C!-- Bottom nav: thumb-friendly, primary destinations -->\n\u003Cnav style=\"position: fixed; bottom: 0; left: 0; right: 0;\">\n  \u003C!-- 3-5 destinations, evenly spaced, 56px+ tall -->\n\u003C\u002Fnav>\n\n\u003C!-- FAB: bottom-right for right-handed primary action -->\n\u003Cbutton style=\"position: fixed; bottom: 24px; right: 24px; width: 56px; height: 56px; border-radius: 28px;\">\n  \u003CPlusIcon \u002F>\n\u003C\u002Fbutton>\n```\n\n## Occlusion (the finger covers the target)\n\nOnce the user's finger touches the screen, it covers the target. A few consequences:\n\n- **Confirm visually after touch, not just on touch-up.** The user wants to know the press registered before they lift.\n- **Don't rely on the user reading text under their finger.** Tooltips, micro-confirmations, \"what does this do?\" hints under the touch point are invisible.\n- **Touch targets should provide visual state changes that radiate beyond the finger** — color flash on the whole row, a ripple effect, an outline that extends past the contact area.\n\nMaterial Design's ripple effect is a classic occlusion-mitigation: the ripple expands outward from the touch point, providing visible feedback that survives the finger's presence.\n\n```css\n@keyframes ripple {\n  to { transform: scale(4); opacity: 0; }\n}\n.button-pressed::after {\n  content: '';\n  position: absolute;\n  border-radius: 50%;\n  background: currentColor;\n  opacity: 0.2;\n  animation: ripple 600ms;\n}\n```\n\n## Edge gestures and the safe area\n\nModern phones use the screen edges for system gestures (back-swipe, app-switcher, control-center). A button placed at the absolute edge competes with these gestures.\n\n**Practical rule:** keep an 8–16px inset from the edges for primary interactive content. Use the system's safe-area insets for top notch and bottom home-indicator clearance:\n\n```css\n.bottom-bar {\n  padding-bottom: env(safe-area-inset-bottom);\n}\n.top-bar {\n  padding-top: env(safe-area-inset-top);\n}\n```\n\nThe screen-edge Fitts-Law advantage still works for *layout* (a tap target abutting the edge is large in one dimension), but *interaction* must respect system gestures.\n\n## Hover states (and why they don't translate)\n\nTouch devices have no hover. UI patterns that rely on hover-revealed actions (a row's \"Edit\" \u002F \"Delete\" buttons that appear on cursor over) silently fail on touch. Mitigations:\n\n- **Always-visible row actions** (perhaps dimmed; see below). Touch users see and can tap them.\n- **Press-and-hold** to reveal a context menu (analogous to right-click).\n- **Swipe gestures** for revealed actions (iOS-style swipe-to-delete on a list row).\n\nDon't ship \"hover to discover the action\" patterns to mobile.\n\n## Worked examples\n\n### Example 1: a row in a list with an action button\n\n**Anti-pattern (mouse-only):**\n\n```html\n\u003Cli class=\"list-item\">\n  \u003Cspan>Project Acme\u003C\u002Fspan>\n  \u003Cbutton class=\"hover-only\" style=\"opacity: 0;\">Open\u003C\u002Fbutton>\n\u003C\u002Fli>\n\u003Cstyle>\n  .list-item:hover .hover-only { opacity: 1; }\n\u003C\u002Fstyle>\n```\n\nOn touch, the button is invisible — and even if you tap it, you can't see it.\n\n**Right (touch-friendly):**\n\n```html\n\u003Cli class=\"list-item\" style=\"display: flex; align-items: center; padding: 12px 16px; min-height: 56px;\">\n  \u003Cspan style=\"flex: 1;\">Project Acme\u003C\u002Fspan>\n  \u003Cbutton aria-label=\"Open Acme\" style=\"width: 44px; height: 44px;\">\n    \u003CChevronRightIcon \u002F>\n  \u003C\u002Fbutton>\n\u003C\u002Fli>\n```\n\nThe action is always visible; the row itself meets the 44px height minimum (56px is even better).\n\n### Example 2: a numeric stepper\n\n```html\n\u003Cdiv class=\"stepper\" style=\"display: inline-flex; align-items: center; gap: 12px;\">\n  \u003Cbutton aria-label=\"Decrease\" style=\"width: 44px; height: 44px;\">−\u003C\u002Fbutton>\n  \u003Cinput type=\"number\" value=\"1\" style=\"width: 60px; height: 44px; text-align: center;\" \u002F>\n  \u003Cbutton aria-label=\"Increase\" style=\"width: 44px; height: 44px;\">+\u003C\u002Fbutton>\n\u003C\u002Fdiv>\n```\n\nBoth buttons are 44×44 with 12px gap to the input — generous spacing prevents misclicks.\n\n### Example 3: a floating action button (FAB)\n\n```html\n\u003Cbutton class=\"fab\" aria-label=\"New post\" style=\"\n  position: fixed;\n  bottom: calc(24px + env(safe-area-inset-bottom));\n  right: 24px;\n  width: 56px; height: 56px;\n  border-radius: 28px;\n  background: var(--brand);\n  color: white;\n  display: grid; place-items: center;\n  box-shadow: 0 4px 12px rgba(0,0,0,0.15);\n\">\n  \u003CPlusIcon \u002F>\n\u003C\u002Fbutton>\n```\n\nBottom-right for thumb reach. 56×56 hit area. Safe-area-inset for home-indicator clearance. Subtle shadow because FABs *do* float above content.\n\n### Example 4: a tab bar\n\n```html\n\u003Cnav class=\"tab-bar\" style=\"\n  position: fixed; bottom: 0; left: 0; right: 0;\n  display: grid; grid-template-columns: repeat(5, 1fr);\n  height: calc(56px + env(safe-area-inset-bottom));\n  padding-bottom: env(safe-area-inset-bottom);\n  background: white;\n  border-top: 1px solid hsl(0 0% 90%);\n\">\n  \u003Cbutton class=\"tab\" aria-current=\"page\">\n    \u003CHomeIcon style=\"width: 24px; height: 24px;\" \u002F>\n    \u003Cspan style=\"font-size: 10px;\">Home\u003C\u002Fspan>\n  \u003C\u002Fbutton>\n  \u003C!-- four more tabs -->\n\u003C\u002Fnav>\n\n\u003Cstyle>\n  .tab {\n    display: grid; place-items: center; gap: 2px;\n    border: 0; background: transparent;\n    color: hsl(0 0% 50%);\n  }\n  .tab[aria-current=\"page\"] { color: var(--brand); }\n\u003C\u002Fstyle>\n```\n\n5 tabs across the bottom. Each tab gets ~76px width × 56px height — generously above 44×44.\n\n## Anti-patterns\n\n- **Tiny X close on a popover.** A 16×16 X in the corner. On touch, nearly impossible to hit reliably.\n- **Stacked menu items at 32px row height.** The user means to tap \"Settings\" and gets \"Sign out.\" Make rows ≥ 44px (preferably 48–56px) on touch.\n- **Edge-flush primary actions.** A \"Send\" button at the absolute right edge that triggers the system back-gesture instead. Inset 8–16px.\n- **Hover-only actions.** Row actions, contextual menus, tooltips that only appear on cursor-over. Either always-visible or accessible via tap-to-reveal.\n- **Inert spacing.** A 44×44 visual button with only 16×16 of actual touchable area (because some CSS issue). Audit with browser DevTools' touch emulator.\n\n## Heuristics\n\n1. **The thumb test.** Hold your phone one-handed, naturally. Try to tap every primary action. Anything that requires a hand-shift is wrong-position.\n2. **The fingertip overlay.** In design comps, overlay a 44×44 circle on every interactive element. Anything where the circle exceeds the visual element's bounds is fine; anything smaller than the circle is too small.\n3. **Real-device testing on the smallest target screen.** A design that works on a Pixel 7 may fail on a small Android device or iPhone SE. Test on actual hardware in actual hands.\n4. **The bystander test.** Watch someone else use your app. Where do they hesitate or correct themselves? Each correction is a Fitts-or-occlusion failure.\n\n## Related sub-skills\n\n- **`fitts-law`** (parent).\n- **`fitts-law-screen-edges`** — companion for desktop; some overlap on mobile (safe areas).\n- **`affordance`** (parent plugin) — touch targets need visual affordance to be discoverable.\n- **`accessibility-operable`** (process plugin) — touch target sizes are an accessibility minimum; don't go below.\n","# Fitts's Law for touch targets\n\nThe finger is a much wider, much less precise pointer than a mouse cursor. Fitts's Law still applies, but the constants change dramatically — and a few touch-specific phenomena (occlusion, thumb reach, edge gestures) layer on top. This skill covers the practical rules.\n\n## Minimum sizes\n\nEvery major touch platform publishes a recommended minimum. They converge:\n\n| Platform \u002F spec | Minimum target | Notes |\n|---|---|---|\n| **Apple HIG (iOS)** | 44×44 pt | The most-cited number; matches average finger contact. |\n| **Material Design (Android)** | 48×48 dp | Roughly equivalent to Apple's 44pt at common densities. |\n| **Microsoft (Windows touch)** | 40×40 effective px | Slightly smaller; Microsoft's research basis. |\n| **WCAG 2.5.5 (Level AAA)** | 44×44 CSS px | Strictest accessibility minimum. |\n| **WCAG 2.5.8 (Level AA, 2.2)** | 24×24 CSS px (with adequate spacing) | Newer, more lenient minimum. |\n\nThe practical rule: **44×44 CSS pixels for any touchable element**. This is the safe number across platforms and accessibility levels. Going smaller is occasionally defensible in specific dense expert contexts; never as a default.\n\nThe visible *icon* inside the button can be smaller (16–24px is common). The *hit area* — the actual touchable region — is what 44×44 measures.\n\n```css\n\u002F* Right: a small icon with a generous tap area *\u002F\n.icon-button {\n  display: inline-grid;\n  place-items: center;\n  width: 44px;\n  height: 44px;\n  padding: 10px;        \u002F* keeps icon centered while tap area stays at 44 *\u002F\n  border: 0;\n  background: transparent;\n  border-radius: 22px;\n}\n.icon-button svg { width: 20px; height: 20px; }\n```\n\n## Spacing between targets\n\nFitts's Law is about acquiring *one* target. When targets are clustered, *spacing* between them prevents accidental neighbor-taps. The convention:\n\n- **At least 8px of clear space** between adjacent touch targets.\n- **44×44 hit area applies to each target**, even if visually they overlap (e.g., padded buttons share visual edges).\n\nFor dense clusters (chip rows, segmented controls), increase visual differentiation: bordered, with internal padding, with adequate gap.\n\n## The thumb-reach map\n\nWhen a phone is held one-handed, the thumb can reach some screen regions easily and others only with strain. Research (Hoober and others) maps this:\n\n```\n+--------------------+\n|       hard         |  \u003C- top of screen, far from thumb base\n|   hard | medium    |\n| medium | easy      |\n| medium | easy      |\n| medium | easy      |  \u003C- bottom-right (right hand) is easiest\n+--------------------+\n```\n\nFor right-handed users, the bottom-right of the screen is easiest; the top-left is hardest. Left-handed users mirror.\n\n**Practical implications:**\n\n- **Primary actions go in the lower portion of the screen.** Floating action buttons (FAB) at bottom-right are a strong Fitts-and-thumb-reach win.\n- **Bottom navigation beats top navigation** for high-frequency tap-to-navigate patterns.\n- **Top-bar actions should be infrequent or hand-agnostic** (search, settings, profile menu — not \"save\" or \"publish\").\n- **Reachability features** (iOS double-tap-home; Android one-handed mode) exist because top corners are genuinely hard.\n\n```html\n\u003C!-- Bottom nav: thumb-friendly, primary destinations -->\n\u003Cnav style=\"position: fixed; bottom: 0; left: 0; right: 0;\">\n  \u003C!-- 3-5 destinations, evenly spaced, 56px+ tall -->\n\u003C\u002Fnav>\n\n\u003C!-- FAB: bottom-right for right-handed primary action -->\n\u003Cbutton style=\"position: fixed; bottom: 24px; right: 24px; width: 56px; height: 56px; border-radius: 28px;\">\n  \u003CPlusIcon \u002F>\n\u003C\u002Fbutton>\n```\n\n## Occlusion (the finger covers the target)\n\nOnce the user's finger touches the screen, it covers the target. A few consequences:\n\n- **Confirm visually after touch, not just on touch-up.** The user wants to know the press registered before they lift.\n- **Don't rely on the user reading text under their finger.** Tooltips, micro-confirmations, \"what does this do?\" hints under the touch point are invisible.\n- **Touch targets should provide visual state changes that radiate beyond the finger** — color flash on the whole row, a ripple effect, an outline that extends past the contact area.\n\nMaterial Design's ripple effect is a classic occlusion-mitigation: the ripple expands outward from the touch point, providing visible feedback that survives the finger's presence.\n\n```css\n@keyframes ripple {\n  to { transform: scale(4); opacity: 0; }\n}\n.button-pressed::after {\n  content: '';\n  position: absolute;\n  border-radius: 50%;\n  background: currentColor;\n  opacity: 0.2;\n  animation: ripple 600ms;\n}\n```\n\n## Edge gestures and the safe area\n\nModern phones use the screen edges for system gestures (back-swipe, app-switcher, control-center). A button placed at the absolute edge competes with these gestures.\n\n**Practical rule:** keep an 8–16px inset from the edges for primary interactive content. Use the system's safe-area insets for top notch and bottom home-indicator clearance:\n\n```css\n.bottom-bar {\n  padding-bottom: env(safe-area-inset-bottom);\n}\n.top-bar {\n  padding-top: env(safe-area-inset-top);\n}\n```\n\nThe screen-edge Fitts-Law advantage still works for *layout* (a tap target abutting the edge is large in one dimension), but *interaction* must respect system gestures.\n\n## Hover states (and why they don't translate)\n\nTouch devices have no hover. UI patterns that rely on hover-revealed actions (a row's \"Edit\" \u002F \"Delete\" buttons that appear on cursor over) silently fail on touch. Mitigations:\n\n- **Always-visible row actions** (perhaps dimmed; see below). Touch users see and can tap them.\n- **Press-and-hold** to reveal a context menu (analogous to right-click).\n- **Swipe gestures** for revealed actions (iOS-style swipe-to-delete on a list row).\n\nDon't ship \"hover to discover the action\" patterns to mobile.\n\n## Worked examples\n\n### Example 1: a row in a list with an action button\n\n**Anti-pattern (mouse-only):**\n\n```html\n\u003Cli class=\"list-item\">\n  \u003Cspan>Project Acme\u003C\u002Fspan>\n  \u003Cbutton class=\"hover-only\" style=\"opacity: 0;\">Open\u003C\u002Fbutton>\n\u003C\u002Fli>\n\u003Cstyle>\n  .list-item:hover .hover-only { opacity: 1; }\n\u003C\u002Fstyle>\n```\n\nOn touch, the button is invisible — and even if you tap it, you can't see it.\n\n**Right (touch-friendly):**\n\n```html\n\u003Cli class=\"list-item\" style=\"display: flex; align-items: center; padding: 12px 16px; min-height: 56px;\">\n  \u003Cspan style=\"flex: 1;\">Project Acme\u003C\u002Fspan>\n  \u003Cbutton aria-label=\"Open Acme\" style=\"width: 44px; height: 44px;\">\n    \u003CChevronRightIcon \u002F>\n  \u003C\u002Fbutton>\n\u003C\u002Fli>\n```\n\nThe action is always visible; the row itself meets the 44px height minimum (56px is even better).\n\n### Example 2: a numeric stepper\n\n```html\n\u003Cdiv class=\"stepper\" style=\"display: inline-flex; align-items: center; gap: 12px;\">\n  \u003Cbutton aria-label=\"Decrease\" style=\"width: 44px; height: 44px;\">−\u003C\u002Fbutton>\n  \u003Cinput type=\"number\" value=\"1\" style=\"width: 60px; height: 44px; text-align: center;\" \u002F>\n  \u003Cbutton aria-label=\"Increase\" style=\"width: 44px; height: 44px;\">+\u003C\u002Fbutton>\n\u003C\u002Fdiv>\n```\n\nBoth buttons are 44×44 with 12px gap to the input — generous spacing prevents misclicks.\n\n### Example 3: a floating action button (FAB)\n\n```html\n\u003Cbutton class=\"fab\" aria-label=\"New post\" style=\"\n  position: fixed;\n  bottom: calc(24px + env(safe-area-inset-bottom));\n  right: 24px;\n  width: 56px; height: 56px;\n  border-radius: 28px;\n  background: var(--brand);\n  color: white;\n  display: grid; place-items: center;\n  box-shadow: 0 4px 12px rgba(0,0,0,0.15);\n\">\n  \u003CPlusIcon \u002F>\n\u003C\u002Fbutton>\n```\n\nBottom-right for thumb reach. 56×56 hit area. Safe-area-inset for home-indicator clearance. Subtle shadow because FABs *do* float above content.\n\n### Example 4: a tab bar\n\n```html\n\u003Cnav class=\"tab-bar\" style=\"\n  position: fixed; bottom: 0; left: 0; right: 0;\n  display: grid; grid-template-columns: repeat(5, 1fr);\n  height: calc(56px + env(safe-area-inset-bottom));\n  padding-bottom: env(safe-area-inset-bottom);\n  background: white;\n  border-top: 1px solid hsl(0 0% 90%);\n\">\n  \u003Cbutton class=\"tab\" aria-current=\"page\">\n    \u003CHomeIcon style=\"width: 24px; height: 24px;\" \u002F>\n    \u003Cspan style=\"font-size: 10px;\">Home\u003C\u002Fspan>\n  \u003C\u002Fbutton>\n  \u003C!-- four more tabs -->\n\u003C\u002Fnav>\n\n\u003Cstyle>\n  .tab {\n    display: grid; place-items: center; gap: 2px;\n    border: 0; background: transparent;\n    color: hsl(0 0% 50%);\n  }\n  .tab[aria-current=\"page\"] { color: var(--brand); }\n\u003C\u002Fstyle>\n```\n\n5 tabs across the bottom. Each tab gets ~76px width × 56px height — generously above 44×44.\n\n## Anti-patterns\n\n- **Tiny X close on a popover.** A 16×16 X in the corner. On touch, nearly impossible to hit reliably.\n- **Stacked menu items at 32px row height.** The user means to tap \"Settings\" and gets \"Sign out.\" Make rows ≥ 44px (preferably 48–56px) on touch.\n- **Edge-flush primary actions.** A \"Send\" button at the absolute right edge that triggers the system back-gesture instead. Inset 8–16px.\n- **Hover-only actions.** Row actions, contextual menus, tooltips that only appear on cursor-over. Either always-visible or accessible via tap-to-reveal.\n- **Inert spacing.** A 44×44 visual button with only 16×16 of actual touchable area (because some CSS issue). Audit with browser DevTools' touch emulator.\n\n## Heuristics\n\n1. **The thumb test.** Hold your phone one-handed, naturally. Try to tap every primary action. Anything that requires a hand-shift is wrong-position.\n2. **The fingertip overlay.** In design comps, overlay a 44×44 circle on every interactive element. Anything where the circle exceeds the visual element's bounds is fine; anything smaller than the circle is too small.\n3. **Real-device testing on the smallest target screen.** A design that works on a Pixel 7 may fail on a small Android device or iPhone SE. Test on actual hardware in actual hands.\n4. **The bystander test.** Watch someone else use your app. Where do they hesitate or correct themselves? Each correction is a Fitts-or-occlusion failure.\n\n## Related sub-skills\n\n- **`fitts-law`** (parent).\n- **`fitts-law-screen-edges`** — companion for desktop; some overlap on mobile (safe areas).\n- **`affordance`** (parent plugin) — touch targets need visual affordance to be discoverable.\n- **`accessibility-operable`** (process plugin) — touch target sizes are an accessibility minimum; don't go below.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Ffitts-law-touch-targets",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fitts-law-touch-targets",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fitts-law-touch-targets",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fitts-law-touch-targets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Ffitts-law-touch-targets\u002FSKILL.md",true,[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Ftouch-research.md","REFERENCE","参考文档",4835,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Ffitts-law-touch-targets\u002Freferences\u002Ftouch-research.md",[82,92,100,108,116,124],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":91},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":91},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":91},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":91},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":91},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]