Agent skill

Android Mobile UI Design

by ModinMobileSTS in ModinMobileSTS/SlayTheAmethystModded

Designs and reviews Android screens with attention to touch ergonomics, adaptive layouts, accessibility, state handling and an implementation handoff.

Custom licenceAuto-check passedMobile

Install Android Mobile UI Design

skills CLI
$ npx skills add ModinMobileSTS/SlayTheAmethystModded --skill android-mobile-frontend-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ModinMobileSTS/SlayTheAmethystModded android-mobile-frontend-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ModinMobileSTS/SlayTheAmethystModded.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/android-mobile-frontend-design .claude/skills/android-mobile-frontend-design && rm -rf skills-src

Use ~/.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/

Facts

Skill name
android-mobile-frontend-design
GitHub stars
403
Token cost
~1k tokens
SKILL.md length
517 words
Files
2
Skills in repo
4
Repo updated
First seen
Licence
Custom licence

At a glance

Designs and reviews Android screens with attention to touch ergonomics, adaptive layouts, accessibility, state handling and an implementation handoff.

  • Works in 5 steps: Identify the product goal, primary user… → Ground the design in the existing app… → Optimize the first-use path, error… → …
  • Designing a new Android screen from product requirements
  • SKILL.md covers Quick Start, Workflow, Android Heuristics and Response Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Design starts with the product goal, the user's main task and the Android surface: phone, tablet, foldable, embedded WebView or a Compose and View hybrid. The skill grounds the design in the existing app's theme, navigation and components before suggesting new patterns, and avoids introducing a new design language unless a redesign is requested.

Work follows five stages. Understand the screen and the main user intent, fit the existing app including back handling, system bars and keyboard insets, design the layout with the primary task above decoration and responsive constraints instead of fixed sizes, define states such as loading, empty, offline, retry and destructive confirmation, then check accessibility and input, with at least 48dp touch targets, screen reader support and labels for icon-only actions.

It also looks at one-handed reach, content density and behavior across small phones, large phones, tablets, foldables, landscape, font scaling and display cutouts, and ends with concrete implementation guidance: layout structure, component behavior, state model and validation criteria.

When your agent uses it

  • Designing a new Android screen from product requirements
  • Critiquing an Android flow for touch ergonomics and empty or error states
  • Making a layout work on tablets, foldables and large font sizes
  • Handing a design to developers with state and validation notes

Example prompts

  • “Design the checkout screen for our Android app, including loading, error and empty states.”
  • “Review this settings flow for one-handed reach and accessibility.”
  • “Turn these product requirements into Android-ready layout and state guidance.”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify the product goal, primary user task, and Android surface: phone, tablet, foldable, embedded WebView, or Compose/View hybrid.
  2. Ground the design in the existing app structure, theme, navigation model, and component system before proposing new patterns.
  3. Optimize the first-use path, error states, empty states, loading states, and recovery paths, not only the happy path.
  4. Check touch ergonomics, one-handed reach, visual hierarchy, content density, accessibility, and responsiveness across common screen sizes.
  5. End with concrete implementation guidance: layout structure, component behavior, state model, and validation criteria.

What it can do on your machine

Read from SKILL.md and the folder at commit cc0f053. 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

Android Mobile UI Design loads about 1k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 517 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~1k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 517 words (~1,039 tokens).

name
android-mobile-frontend-design

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in .opencode/skills/android-mobile-frontend-design of ModinMobileSTS/SlayTheAmethystModded.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit cc0f053

Compare with similar skills

Android Mobile UI Design 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.

Android Mobile UI Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Android Mobile UI Design this skillModinMobileSTS/SlayTheAmethystModded403—~1kAutomated safety check: PassCustom licence
Android UXrcosteira79/android-skills153—~2.3kAutomated safety check: PassMIT
Accessible Mobile DeveloperFerroxLabs/wayland608—~3.6kAutomated safety check: PassApache-2.0
Material 3hamen/material-3-skill1.5k2 repos~7.8kAutomated safety check: PassMIT
Android UI AutomationOpenMinis/MinisSkills444—~1.6kAutomated safety check: PassMIT
Android AccessibilityMoustachauve/WLED-Android1693 repos~471Automated safety check: PassApache-2.0

Similar skills

  • Android UX

    rcosteira79/android-skills

    A skill your agent uses when designing or reviewing Android UI — applies Material Design 3 UX principles covering touch targets, spacing, navigation patterns, accessibility, animation timing, and…

    153 GitHub stars~2.3k tokensUpdated 20 days ago
    Frontend & DesignAuto-check passed
  • Accessible Mobile Developer

    FerroxLabs/wayland

    Mobile accessibility development expertise covering iOS VoiceOver and Android TalkBack integration, accessibility APIs for SwiftUI and Jetpack Compose, touch target sizing, gesture alternatives…

    608 GitHub stars~3.6k tokensUpdated 3 days ago
    MobileAuto-check passed
  • Material 3

    hamen/material-3-skill

    Implement Google's Material Design 3 (Material You) UI system.

    1.5k GitHub starsUsed in 2 repos~7.8k tokens
    Frontend & DesignAuto-check passed
  • Android UI Automation

    OpenMinis/MinisSkills

    Automate Android apps that have no public API or web version by driving the UI layer through the Accessibility Service.

    444 GitHub stars~1.6k tokensUpdated 2 days ago
    MobileAuto-check passed
  • Android Accessibility

    Moustachauve/WLED-Android

    Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.

    169 GitHub starsUsed in 3 repos~471 tokens
    Frontend & DesignAuto-check passed
  • Configuring Test Dependencies

    skydoves/android-testing-skills

    A skill your agent uses to wire the correct Gradle dependency matrix for Jetpack Compose UI tests.

    333 GitHub stars~4.1k tokensUpdated 4 mo ago
    MobileAuto-check passed

More from ModinMobileSTS/SlayTheAmethystModded

  • Slay the Amethyst Feedback Diagnosis

    ModinMobileSTS/SlayTheAmethystModded

    Reads Slay the Amethyst diagnostics bundles to decide whether a problem comes from the launcher, a mod or the device, citing exact files and lines.

    403 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed
  • Compose Performance Audit

    ModinMobileSTS/SlayTheAmethystModded

    Audits Jetpack Compose screens for performance problems, from recomposition scope and stability to lazy list keys and effects, and proposes minimal fixes with ways to verify them.

    403 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Jetpack Compose Patterns

    ModinMobileSTS/SlayTheAmethystModded

    Applies practical Jetpack Compose patterns to Android UI code: state hoisting, one-way data flow, side effects, modifiers, theming and testable composables.

    403 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Android Mobile UI Design

What does Android Mobile UI Design do?

Designs and reviews Android screens with attention to touch ergonomics, adaptive layouts, accessibility, state handling and an implementation handoff. Design starts with the product goal, the user's main task and the Android surface: phone, tablet, foldable, embedded WebView or a Compose and View hybrid. The skill grounds the design in the existing app's theme, navigation and components before suggesting new patterns, and avoids introducing a new design language unless a redesign is requested.

When should I use Android Mobile UI Design?

Android Mobile UI Design fits situations like: designing a new Android screen from product requirements; critiquing an Android flow for touch ergonomics and empty or error states; making a layout work on tablets, foldables and large font sizes; handing a design to developers with state and validation notes.

How do I install Android Mobile UI Design in Claude Code?

Run `npx skills add ModinMobileSTS/SlayTheAmethystModded --skill android-mobile-frontend-design -a claude-code`. Or copy the skill folder (.opencode/skills/android-mobile-frontend-design in ModinMobileSTS/SlayTheAmethystModded) into .claude/skills/android-mobile-frontend-design in your project. Claude Code loads it when a task matches its description.

How do I install Android Mobile UI Design in Codex?

Run `npx skills add ModinMobileSTS/SlayTheAmethystModded --skill android-mobile-frontend-design -a codex`. Or copy the skill folder (.opencode/skills/android-mobile-frontend-design in ModinMobileSTS/SlayTheAmethystModded) into .agents/skills/android-mobile-frontend-design in your project. Codex loads it when a task matches its description.

Can I use Android Mobile UI Design 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 ModinMobileSTS/SlayTheAmethystModded --skill android-mobile-frontend-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/android-mobile-frontend-design, .gemini/skills/android-mobile-frontend-design, .github/skills/android-mobile-frontend-design and .opencode/skills/android-mobile-frontend-design in your project.

What does Android Mobile UI Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Android Mobile UI Design is instructions for the agent only.

Does Android Mobile UI Design 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 Android Mobile UI Design 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 Android Mobile UI Design use?

Android Mobile UI Design has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Android Mobile UI Design use?

About 1k tokens (SKILL.md is roughly 4.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 Android Mobile UI Design?

Skills that share tags, products or a category with Android Mobile UI Design: Android UX (rcosteira79/android-skills, 153 stars), Accessible Mobile Developer (FerroxLabs/wayland, 608 stars), Material 3 (hamen/material-3-skill, 1.5k stars) and Android UI Automation (OpenMinis/MinisSkills, 444 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Android Mobile UI Design?

ModinMobileSTS (a GitHub organization) maintains it in ModinMobileSTS/SlayTheAmethystModded, which has 403 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.

Source: ModinMobileSTS/SlayTheAmethystModded on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.