From tonone
Provides iOS and Android mobile UI guidelines on touch targets, platform rules, navigation, forms, and gestures via knowledge base search. Activates for mobile UI queries.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tonone:touch-uiThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
User asks about mobile UI, touch targets, platform conventions, or mobile interaction patterns.
python3 -m touch_agent.uiux search --domain app-interface --query "{platform} {topic}" --limit 5
python3 -m touch_agent.uiux search --domain stacks --query "{framework}" --limit 3
┌─ Mobile UI Guidelines — {platform} ─────────────────────────────────┐
│ Rule │ Spec │ Severity │
├────────────────────────┼─────────────────────────┼───────────────────┤
│ Touch target min size │ 44×44pt (iOS) │ Critical │
│ Touch target min size │ 48×48dp (Android) │ Critical │
│ {rule} │ {spec} │ {severity} │
└────────────────────────┴─────────────────────────┴───────────────────┘
Code example ({platform}):
{code_block}
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
npx claudepluginhub tonone-ai/tonone --plugin eval-regressGuides mobile-first, touch-first design for iOS/Android apps with MFRI risk assessment and mandatory checklists to prevent desktop assumptions.
Guides iOS app development per Apple's Human Interface Guidelines, covering interface design, accessibility (VoiceOver, Dynamic Type), dark mode, touch targets, animations, haptics, and permissions.
Enforces mobile-first, touch-first, platform-respectful design. Prevents desktop-thinking defaults by assessing feasibility, interaction complexity, and offline needs.