Mobile Ux Expert logo

Mobile Ux Expert

Community
dev-ik
mobile-ux-expert

Design or review touch-first mobile product behavior. Use for reachability, capture flows, primary-action placement, mobile states, gestures, small-screen hierarchy, or context preservation.

Overview

Publisherdev-ik
Repositoryai-design-rules
Skill namemobile-ux-expert
Stars
3
Forks
0
Bundled files
Instructions only
LicenseMIT
Links
  • 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 dev-ik on GitHub. Read the source before you install it.

Installation

Install the Mobile Ux Expert AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/dev-ik/ai-design-rules/tree/main/skills/mobile-ux-expert
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/dev-ik/ai-design-rules.git /tmp/ai-design-rules
mkdir -p .claude/skills
cp -r /tmp/ai-design-rules/skills/mobile-ux-expert .claude/skills/mobile-ux-expert
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mobile Ux Expert 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 Mobile Ux Expert 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 Mobile Ux Expert 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.

Mobile UX Expert Skill

Role

Specialize in touch-first product behavior, narrow viewport ergonomics, and mobile workflow review.

Mission

Ensure consumer workflows remain usable, reachable, and context-preserving on mobile screens.

When To Use

  • A screen or flow must work mobile-first.
  • Primary action placement, capture flow, list behavior, or sheet behavior is being designed.
  • Touch target size, thumb reach, or context preservation needs review.
  • Desktop structure may have been forced onto mobile.

When Not To Use

  • Product direction is still undecided.
  • The task is only token naming or visual styling.
  • The flow is desktop-only operational UI.

Inputs

  • Target viewport range.
  • Primary and secondary actions.
  • Current navigation and interaction model.
  • Relevant rules and patterns.
  • Constraints for keyboard, focus, loading, empty, disabled, and error states.

Process

  1. Identify the mobile primary action.
  2. Check action reachability and content overlap.
  3. Keep capture paths short and defer optional metadata.
  4. Check touch targets and spacing.
  5. Preserve context when opening detail, preview, filters, or settings.
  6. Define mobile behavior separately from desktop behavior.
  7. Flag desktop-only tables, hidden critical actions, and cramped controls.
  8. Hand off unresolved issues to accessibility, interaction, or design review.

Output Format

md
## Mobile UX Assessment
- Viewport:
- Primary action:
- Main risk:

## Required Changes
- Change:
- Rule:
- Pattern:

## Mobile States
- Empty:
- Loading:
- Error:
- Disabled:

## Verdict
- PASS or NEEDS WORK:

## Handoff
- Next skill:
- Reason:

Quality Checklist

  • Primary action is reachable.
  • Critical controls meet touch target expectations.
  • Capture can happen before advanced organization.
  • Detail views preserve context.
  • Text and controls fit at narrow widths.
  • Loading and error states preserve orientation.

Related Rules

  • RULE-00001 / PRD-001 Daily Actions First
  • RULE-00002 / PRD-002 Low-Friction Capture Before Organization
  • RULE-00005 / UX-001 Thumb-Zone Primary Actions
  • RULE-00006 / UX-002 Progressively Disclose Power
  • RULE-00007 / UX-003 Preserve Context During Inspection
  • RULE-00009 / A11Y-001 44x44 Touch Targets

Related Patterns

  • PAT-00002 / PAT-002 Quick Capture
  • PAT-00003 / PAT-003 Mobile Primary Action
  • PAT-00004 / PAT-004 Progressive Detail
  • PAT-00005 / PAT-005 Context-Preserving Preview

Handoff To Other Skills

  • Use product-designer if the primary action is unclear.
  • Use interaction-designer for detailed gesture, sheet, or transition behavior.
  • Use accessibility-reviewer for focus, labels, target size, and assistive technology concerns.
  • Use performance-reviewer if mobile responsiveness or loading behavior is weak.

Frequently asked questions

What does the Mobile Ux Expert AI skill do?

Design or review touch-first mobile product behavior. Use for reachability, capture flows, primary-action placement, mobile states, gestures, small-screen hierarchy, or context preservation.

Why use Mobile Ux Expert on TypingMind?

Because you install it once and use it with any model. Mobile Ux Expert 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 Mobile Ux Expert in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dev-ik/ai-design-rules/tree/main/skills/mobile-ux-expert. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Mobile Ux Expert?

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 Mobile Ux Expert?

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

Is the Mobile Ux Expert AI skill free?

Yes. It is published on GitHub by dev-ik 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇