touch-ui
Use when asked about mobile UI guidelines, touch targets, platform-specific UI rules, or mobile interaction patterns. Examples: "iOS touch targets", "Android UI guidelines", "mobile form design"
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- touch-ui
- tags
- [ "engineering", "mobile", "ui" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 0.6.6
- description
- Use when asked about mobile UI guidelines, touch targets, platform-specific UI rules, or mobile interaction patterns. Examples: "iOS touch targets", "Android UI guidelines", "mobile form design"
- allowed-tools
- Read, Bash, Glob, Grep
- compatibility
- Designed for Claude Code
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
touch-ui — Mobile UI Guidelines
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
When to use
User asks about mobile UI, touch targets, platform conventions, or mobile interaction patterns.
Workflow
- Identify platform and topic from user request (iOS / Android / cross-platform; touch targets, navigation, forms, gestures, etc.)
- Search app-interface knowledge base:
python3 -m touch_agent.uiux search --domain app-interface --query "{platform} {topic}" --limit 5 - Search stack conventions if framework is mentioned:
python3 -m touch_agent.uiux search --domain stacks --query "{framework}" --limit 3 - Output platform-specific rules with code examples
Output format
┌─ 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}
Anti-patterns
- Never apply iOS Human Interface Guidelines patterns on Android (and vice versa)
- Never set touch targets below 44×44pt on iOS or 48×48dp on Android
- Never use hover-dependent interactions on touch-primary interfaces
- Never skip platform detection — always confirm iOS vs. Android before outputting guidelines
Delivery
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.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.