App Store Screenshots Generator
ParthJadhav/app-store-screenshots
Scaffolds a Next.js editor for designing App Store and Google Play screenshots as ads and exporting them at every required size, for iOS, Mac and Android.
Apply medium-specific UX reasoning for MOBILE (phone) applications: touch input, small screen, one-handed use, single-surface focus.
Install UX Mobile
$ npx skills add davidortinau/maui-skills --skill ux-mobile -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davidortinau/maui-skills ux-mobile --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/davidortinau/maui-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/maui-skills/skills/ux-mobile .claude/skills/ux-mobile && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ux-mobile" agent skill from https://github.com/davidortinau/maui-skills/tree/main/plugins/maui-skills/skills/ux-mobile into .claude/skills/ux-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ux-mobile", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/davidortinau/maui-skills/tree/main/plugins/maui-skills/skills/ux-mobileType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add davidortinau/maui-skills --skill ux-mobile -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davidortinau/maui-skills ux-mobile --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davidortinau/maui-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/maui-skills/skills/ux-mobile .agents/skills/ux-mobile && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ux-mobile" agent skill from https://github.com/davidortinau/maui-skills/tree/main/plugins/maui-skills/skills/ux-mobile into .agents/skills/ux-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ux-mobile", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davidortinau/maui-skills --skill ux-mobile -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davidortinau/maui-skills ux-mobile --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davidortinau/maui-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/maui-skills/skills/ux-mobile .cursor/skills/ux-mobile && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ux-mobile" agent skill from https://github.com/davidortinau/maui-skills/tree/main/plugins/maui-skills/skills/ux-mobile into .cursor/skills/ux-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ux-mobile", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/davidortinau/maui-skills.git --path plugins/maui-skills/skills/ux-mobile--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add davidortinau/maui-skills --skill ux-mobile -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davidortinau/maui-skills ux-mobile --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davidortinau/maui-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/maui-skills/skills/ux-mobile .gemini/skills/ux-mobile && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ux-mobile" agent skill from https://github.com/davidortinau/maui-skills/tree/main/plugins/maui-skills/skills/ux-mobile into .gemini/skills/ux-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ux-mobile", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install davidortinau/maui-skills ux-mobileInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add davidortinau/maui-skills --skill ux-mobile -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davidortinau/maui-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/maui-skills/skills/ux-mobile .github/skills/ux-mobile && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ux-mobile" agent skill from https://github.com/davidortinau/maui-skills/tree/main/plugins/maui-skills/skills/ux-mobile into .github/skills/ux-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ux-mobile", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davidortinau/maui-skills --skill ux-mobile -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install davidortinau/maui-skills ux-mobile --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davidortinau/maui-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/maui-skills/skills/ux-mobile .opencode/skills/ux-mobile && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ux-mobile" agent skill from https://github.com/davidortinau/maui-skills/tree/main/plugins/maui-skills/skills/ux-mobile into .opencode/skills/ux-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ux-mobile", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ux-mobile- GitHub stars
- 175
- Token cost
- ~1.3k tokens
- SKILL.md length
- 663 words
- Files
- 1
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- MIT
At a glance
Apply medium-specific UX reasoning for MOBILE (phone) applications: touch input, small screen, one-handed use, single-surface focus.
- Works in 6 steps: Target sizing is a floor, not a budget.… → There is no hover. The finger is either… → Screen real estate is scarce — density… → …
- : design a mobile screen
- SKILL.md covers What defines the mobile medium, The six things that change, How principles shift on mobile and Render-time platform handoff…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
UX Mobile is an agent skill from davidortinau/maui-skills. Apply medium-specific UX reasoning for MOBILE (phone) applications: touch input, small screen, one-handed use, single-surface focus. Use alongside ux-first-principles when the target is a phone app (iOS or Android) and the decision is affected by touch target sizing, the absence of hover, thumb reach, limited screen real estate, or single-task focus. USE FOR: 'design a mobile screen', 'lay out this phone app', 'what should the mobile navigation be', touch target sizing, thumb-reach layout, single-task handheld…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Mobile, covering Mobile UI design and Real estate. It works with Android and iOS. The repository describes itself as: .NET MAUI skills for GitHub Copilot and Claude Code. The licence is MIT.
When your agent uses it
- : design a mobile screen
- Lay out this phone app
- What should the mobile navigation be
- Touch target sizing
Example prompts
- “design a mobile screen”
- “lay out this phone app”
- “what should the mobile navigation be”
- “/ux-mobile”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Target sizing is a floor, not a budget. A fingertip is roughly 10–14mm wide and occludes the thing it taps. Interactive targets must be…
- There is no hover. The finger is either off the glass or committing to a tap; there is no idle-pointer state. Anything desktop would put…
- Screen real estate is scarce — density must drop. The same content that reads as efficient on desktop reads as cramped and overwhelming on…
- Reach and thumb zones matter. Held one-handed, the thumb comfortably reaches the bottom-center of the screen; the top corners are a…
- Single-surface, single-task focus. One app, fullscreen, one task at a time. Design a focused linear flow rather than the multi-panel…
- Gestures replace precision and right-click. There is no right-click and no fine pointer. Swipe, long-press, pinch, and pull are the…
What it can do on your machine
Read from SKILL.md and the folder at commit 79bb4bf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
UX Mobile loads about 1.3k tokens when it runs. Until then it costs about 183 tokens; SKILL.md has 663 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from davidortinau/maui-skills at commit 79bb4bf, republished under its MIT licence (© davidortinau). 663 words, ~1,302 tokens.
Download SKILL.mdSave it as
.claude/skills/ux-mobile/SKILL.md (or your agent's skills folder).- name
- ux-mobile
- description
- Apply medium-specific UX reasoning for MOBILE (phone) applications: touch input, small screen, one-handed use, single-surface focus. Use alongside ux-first-principles when the target is a phone app (iOS or Android) and the decision is affected by touch target sizing, the absence of hover, thumb reach, limited screen real estate, or single-task focus. USE FOR: 'design a mobile screen', 'lay out this phone app', 'what should the mobile navigation be', touch target sizing, thumb-reach layout, single-task handheld flows. DO NOT USE FOR: the invariant principles (use ux-first-principles); desktop or tablet layouts (use ux-desktop or ux-tablet); picking colors, fonts, or platform chrome (use a styling/execution skill).
UX for Mobile (Phone)
A thin medium layer. The reasoning lives in ux-first-principles; read it first or alongside. Here is only what the phone medium changes — driven by the body-to-device interface, not by which OS it is.
What defines the mobile medium
A coarse touch input (fingertip, not a point), a small screen held at arm's length, frequent one-handed and on-the-move use, and a single app in focus filling the screen. These change six things — and several are the mirror image of desktop.
The six things that change
Target sizing is a floor, not a budget. A fingertip is roughly 10–14mm wide and occludes the thing it taps. Interactive targets must be large and well-spaced or users mis-tap. Treat a generous minimum tap target as a hard floor and add spacing between adjacent targets to prevent errors. You cannot use the dense, tiny controls that work on desktop. (The exact minimum is a platform metric — see handoff.)
There is no hover. The finger is either off the glass or committing to a tap; there is no idle-pointer state. Anything desktop would put behind hover — tooltips, reveal-on-hover controls, hover previews — must not carry essential information or actions on mobile. Surface it persistently, or behind an explicit tap/long-press with a visible signifier. This is the most common porting bug from desktop UI.
Screen real estate is scarce — density must drop. The same content that reads as efficient on desktop reads as cramped and overwhelming on a phone. Reduce per-screen density, shorten navigation depth, and accept more screens / more scrolling rather than packing one. Lead with the single primary task; defer the rest (progressive disclosure is heavily used here).
Reach and thumb zones matter. Held one-handed, the thumb comfortably reaches the bottom-center of the screen; the top corners are a stretch. Put primary, frequent actions in the easy bottom zone; put rare or destructive actions where they're harder to hit by accident. This consideration has no desktop analog — the cursor reaches every pixel equally.
Single-surface, single-task focus. One app, fullscreen, one task at a time. Design a focused linear flow rather than the multi-panel, multi-window layouts desktop affords. Carry context forward between screens so users don't have to remember it (Miller's Law, recognition over recall — recall is costlier on mobile because there's no room to keep things visible).
Gestures replace precision and right-click. There is no right-click and no fine pointer. Swipe, long-press, pinch, and pull are the equivalents — but they're invisible unless signified. Provide a visible button path for anything important; never make a hidden gesture the only way to reach an action.
Show full SKILL.md (226 more words)Show less
How principles shift on mobile
- Fitts's Law: target size is now a usability floor; distance matters less than reachability (thumb zones).
- Hick's Law: show fewer choices per screen than desktop — small screens make long option sets punishing.
- Progressive disclosure: your main tool, used aggressively; lead with the common case, defer everything else to taps and subsequent screens.
- Aesthetic-Usability / Peak-End: mobile moments are short and frequent; smooth, fast, focused flows matter more than feature breadth.
Render-time platform handoff (NOT design decisions)
Mechanical per-platform substitutions, handled in styling / at render time (e.g., by .NET MAUI), not reasoned from principles:
- Exact minimum tap-target metric, system fonts, control styling, corner radii, and material/elevation conventions.
- Platform navigation chrome styling and the standard system affordances.
- OS-global gestures: respect the platform's system back / home / edge gestures rather than fighting or overriding them.
Everything else — including structural choices like tab bar vs. navigation drawer, bottom-sheet vs. full screen, and flow depth — is a design decision. Reason it from first principles (information architecture, Hick, hierarchy) and commit to ONE answer; both tabs and drawers are acceptable on either OS, so don't fork the structure per platform.
Deliberate scope note
This optimizes for a coherent cross-platform product over maximal single-OS idiomaticity, which is the right trade-off for cross-platform work. It would only bite an app whose whole value proposition is feeling 100% hand-built-native on one OS.
© davidortinau, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/maui-skills/skills/ux-mobile of davidortinau/maui-skills.
Open the folder on GitHubat commit 79bb4bf
Compare with similar skills
UX Mobile next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| UX Mobile this skilldavidortinau/maui-skills | 175 | — | ~1.3k | Automated safety check: Pass | MIT | |
| App Store Screenshots GeneratorParthJadhav/app-store-screenshots | 7.2k | — | ~16k | Automated safety check: Pass | MIT | |
| Building Native UICherryHQ/cherry-studio-app | 4k | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Phoneagentrounak/PhoneAgent | 800 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Mobile UI Designopenvetta/open-vetta | 290 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Mobile PrinciplesAThevon/genjutsu | 440 | — | ~2.8k | Automated safety check: Pass | Custom licence |
Similar skills
Building Native UI
CherryHQ/cherry-studio-app
Complete guide for building beautiful apps with Expo Router.
Phoneagent
rounak/PhoneAgent
Control a connected iPhone, iOS simulator, Android emulator, or Android device from macOS through PhoneAgent's JSON-RPC bridge.
Mobile UI Design
openvetta/open-vetta
Design mobile-style HTML pages (iOS / Android) for preview in the Mobile UI Preview panel.
Mobile Principles
AThevon/genjutsu
Mobile-specific UX principles - touch targets, hover-less doctrine, thumb zones, safe areas, gestures, mobile perf budgets.
UI Mobile
alinaqi/maggy
Mobile UI patterns - React Native, iOS/Android, touch targets
More from davidortinau/maui-skills
All 41 skills in this repoMaui Hot Reload Diagnostics
davidortinau/maui-skills
Diagnose and troubleshoot .NET MAUI Hot Reload issues (C Hot Reload, XAML Hot Reload, Blazor Hybrid).
Maui Accessibility
davidortinau/maui-skills
Guide for making .NET MAUI apps accessible — screen reader support via SemanticProperties, heading levels, AutomationProperties visibility control, programmatic focus and announcements, and…
Maui Animations
davidortinau/maui-skills
.NET MAUI view animations, custom animations, easing functions, rotation, scale, translation, and fade effects.
Maui App Icons Splash
davidortinau/maui-skills
.NET MAUI app icon configuration, splash screen setup, SVG to PNG conversion at build time, composed/adaptive icons, and platform-specific icon and splash screen requirements for Android, iOS, Mac…
Maui App Lifecycle
davidortinau/maui-skills
.NET MAUI app lifecycle guidance covering the four app states (not running, running, deactivated, stopped), cross-platform Window lifecycle events, backgrounding and resume behaviour…
Maui Aspire
davidortinau/maui-skills
Guide for .NET MAUI apps consuming .NET Aspire-hosted backend services.
Related
Categories
Questions about UX Mobile
What does UX Mobile do?
Apply medium-specific UX reasoning for MOBILE (phone) applications: touch input, small screen, one-handed use, single-surface focus. UX Mobile is an agent skill from davidortinau/maui-skills. Apply medium-specific UX reasoning for MOBILE (phone) applications: touch input, small screen, one-handed use, single-surface focus.
When should I use UX Mobile?
UX Mobile fits situations like: : design a mobile screen; lay out this phone app; what should the mobile navigation be; touch target sizing.
How do I install UX Mobile in Claude Code?
Run `npx skills add davidortinau/maui-skills --skill ux-mobile -a claude-code`. Or copy the skill folder (plugins/maui-skills/skills/ux-mobile in davidortinau/maui-skills) into .claude/skills/ux-mobile in your project. Claude Code loads it when a task matches its description.
How do I install UX Mobile in Codex?
Run `npx skills add davidortinau/maui-skills --skill ux-mobile -a codex`. Or copy the skill folder (plugins/maui-skills/skills/ux-mobile in davidortinau/maui-skills) into .agents/skills/ux-mobile in your project. Codex loads it when a task matches its description.
Can I use UX Mobile in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davidortinau/maui-skills --skill ux-mobile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ux-mobile, .gemini/skills/ux-mobile, .github/skills/ux-mobile and .opencode/skills/ux-mobile in your project.
What does UX Mobile need to run?
SKILL.md names no scripts, command-line tools or credentials: UX Mobile is instructions for the agent only.
Does UX Mobile access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is UX Mobile safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does UX Mobile use?
UX Mobile is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does UX Mobile use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to UX Mobile?
Skills that share tags, products or a category with UX Mobile: App Store Screenshots Generator (ParthJadhav/app-store-screenshots, 7.2k stars), Building Native UI (CherryHQ/cherry-studio-app, 4k stars), Phoneagent (rounak/PhoneAgent, 800 stars) and Mobile UI Design (openvetta/open-vetta, 290 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains UX Mobile?
davidortinau (a GitHub user) maintains it in davidortinau/maui-skills, which has 175 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on July 6, 2026.
Source: davidortinau/maui-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.