Touch Target Design

Community

Owl-Listener

touch-target-design

Design touch targets and pointer interactions that work for people with motor difficulties, tremors, limited dexterity, or who use assistive pointing devices. Use when designing buttons, links, form controls, mobile interfaces, or any clickable/tappable elements. Triggers on: touch target, tap target, button size, too small to tap, fat finger, motor disability, dexterity, tremor, pointer, click area, hit area, mobile buttons.

Overview

Publisher	Owl-Listener
Repository	`inclusive-design-skills`
Skill name	`touch-target-design`
Stars	108
Forks	28
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Touch Target Design AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/touch-target-design
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/touch-target-design

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git /tmp/inclusive-design-skills
mkdir -p .claude/skills
cp -r /tmp/inclusive-design-skills/inclusive-interaction/skills/touch-target-design .claude/skills/touch-target-design

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Touch Target Design in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Touch Target Design on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Touch Target Design is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Touch Target Design

Design interactive elements that are large enough, spaced enough, and forgiving enough for people with limited precision — whether from disability, age, environment, or device.

Minimum Sizes

Touch (mobile, tablet)

Minimum: 44×44 CSS pixels (WCAG 2.2 Level AA)
Recommended: 48×48 CSS pixels (Google Material guidelines)
For high-stakes or frequent-use targets: 56×56 or larger

Pointer (desktop)

Minimum: 24×24 CSS pixels (WCAG 2.2 Level AA)
Recommended: 32×32 for common actions
For destructive or irreversible actions: larger targets reduce errors

Spacing Between Targets

Minimum: 8px gap between adjacent interactive elements
Recommended: 12–16px for frequently used elements side by side
Never place destructive actions (delete) adjacent to common actions (save) without spacing or visual separation

Design Patterns

Generous Hit Areas

The tappable area can be larger than the visible element
Use padding, not just the visual size of the icon or text
Entire row should be tappable in list items, not just the text
Link text should be descriptive enough to form a reasonable tap target ("Read the full report" not "here")

Forgiving Interactions

Don't trigger actions on touch-down — trigger on touch-up (this lets users slide away to cancel)
For destructive actions: require a deliberate second tap or confirmation, not a single tap
Avoid double-tap requirements — they're unreliable for users with tremors
Avoid long-press as the only way to access functionality

Spacing for Safety

Separate "confirm" and "cancel" actions with distance or visual weight
Place destructive actions away from common actions
Group related actions together, separate unrelated actions
On mobile: keep primary actions in the thumb zone (bottom half of screen)

Alternatives to Precision

Provide zoom capability for complex interfaces
Allow pinch-to-zoom on mobile (never disable it)
For precise tasks (colour pickers, sliders): provide a text input alternative
Dropdown menus with many items: add search/filter

Assessment Questions

Are all interactive elements at least 44×44px on touch devices?
Is there adequate spacing between adjacent targets?
Are destructive actions separated from common actions?
Can every interaction be completed without precision timing or precise pointing?
Is there always an alternative to precision-dependent interactions like sliders or drag-and-drop?

Frequently asked questions

What does the Touch Target Design AI skill do?

Why use Touch Target Design on TypingMind?

Because you install it once and use it with any model. Touch Target Design is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Touch Target Design in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/touch-target-design. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Touch Target Design?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Touch Target Design?

As many as you like. As long as a model supports skills, you can use Touch Target Design with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Touch Target Design AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Grill With Docs

mattpocock

CommunityPopular

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Grill Me

A relentless interview to sharpen a plan or design.

Brand Discovery

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Competitive Platform Analysis

affaan-m

CommunityPopular

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Touch Target Design

Minimum Sizes

Touch (mobile, tablet)

Pointer (desktop)

Spacing Between Targets

Design Patterns

Generous Hit Areas

Forgiving Interactions

Spacing for Safety

Alternatives to Precision

Assessment Questions

Frequently asked questions

Related AI Skills

Set up your own AI workspace now