Android UI States Validation
CommunitykrutikJain
Review Android UI flows for empty, loading, error, offline, and edge-case behavior before release.
Overview
- Repository
- krutikJain/android-agent-skills
- Publisher
- krutikJain
- Stars
- 14
- Forks
- 5
- Bundled files
- 5
- License
- MIT
- Updated
- Mar 25, 2026
Installation
tmp=$(mktemp -d)
git clone --depth 1 https://github.com/krutikJain/android-agent-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/android-ui-states-validation" ~/.claude/skills/android-ui-states-validation
rm -rf "$tmp"tmp=$(mktemp -d)
git clone --depth 1 https://github.com/krutikJain/android-agent-skills.git "$tmp"
mkdir -p ~/.codex/skills
cp -R "$tmp/skills/android-ui-states-validation" ~/.codex/skills/android-ui-states-validation
rm -rf "$tmp"Install the Android UI States Validation agent skill from https://github.com/krutikJain/android-agent-skills/tree/main/skills/android-ui-states-validation into this project's skills folder.Instructions
Android UI States Validation
When To Use
- Use this skill when the request is about: validate android ui states, check loading empty error flow android, edge cases in android screen.
- Primary outcome: Review Android UI flows for empty, loading, error, offline, and edge-case behavior before release.
- Reach for this skill when the core question is state coverage and recovery UX, not which test framework or assertion library to use.
- This skill decides what the user should see in each branch of the state matrix.
android-testing-uionly validates that design with assertions and screenshots. - Handoff skills when the scope expands:
android-compose-accessibilityandroid-testing-ui
Workflow
- Confirm the user-visible journey, target device behavior, and failure states that matter.
- Build a state matrix that covers loading, content, empty, error, offline, stale-data, denied-permission, and post-action confirmation states as applicable.
- Identify the owning screens, activities, destinations, and state holders for each branch of that matrix.
- Validate recovery UX, accessibility, configuration changes, and back-stack behavior in the showcase apps.
- Hand off to testing only when the missing work is about assertions or automation rather than state design.
Guardrails
- Treat loading, empty, error, offline, and permission-denied states as first-class UI states.
- Do not hide navigation or permission side effects inside reusable UI components.
- Prefer lifecycle-aware APIs over manual callback chains.
- Keep deep links, intents, and permission prompts testable and observable.
- Distinguish transient messages, persistent error states, and stale-but-usable content instead of collapsing them into one generic failure screen.
Anti-Patterns
- Assuming the happy path is enough for product flows.
- Hard-coding request codes or route strings in multiple places.
- Triggering navigation directly from repositories or network layers.
- Shipping flows without recovery UI for denied permissions or broken state.
- Using tests as a substitute for deciding what the product should show in each failure mode.
Examples
Happy path
- Scenario: Validate OrbitTasks loading, content, and success confirmation states.
- Command:
cd examples/orbittasks-compose && ./gradlew :app:connectedDebugAndroidTest
Edge case
- Scenario: Exercise long content, empty lists, and sync failures in the XML fixture.
- Command:
cd examples/orbittasks-xml && ./gradlew :app:connectedDebugAndroidTest
Failure recovery
- Scenario: Avoid misrouting UI validation work to accessibility or testing-only skills.
- Command:
python3 scripts/eval_triggers.py --skill android-ui-states-validation
Done Checklist
- The implementation path is explicit, minimal, and tied to the right Android surface.
- Relevant example commands and benchmark prompts have been exercised or updated.
- Handoffs to adjacent skills are documented when the request crosses boundaries.
- Official references cover the chosen pattern and the main migration or troubleshooting path.
Official References
Bundled files
FAQ
What does Android UI States Validation do?
Review Android UI flows for empty, loading, error, offline, and edge-case behavior before release.
Who made Android UI States Validation?
krutikJain (a community member) publishes it in the krutikJain/android-agent-skills repository on GitHub.
Is Android UI States Validation free?
Yes. Android UI States Validation is open source, published by krutikJain under the MIT license.
What comes with Android UI States Validation?
Its instructions and 5 files the agent reads only when a task needs them, such as references, examples or scripts.
Which agents can use Android UI States Validation?
Any coding agent that reads SKILL.md files, including Claude Code, Codex, Cursor, GitHub Copilot and Gemini CLI. The agent loads the skill when a task matches its description.
What are agent skills?
An agent skill is a folder with a SKILL.md file: instructions that teach a coding agent how to do one kind of task, and optionally files it can read while it works. The agent keeps only the skill's name and description in mind and reads the rest when a task calls for it.
How are agent skills different from MCP servers?
An MCP server gives an agent new tools to call, code that runs somewhere and returns results. A skill gives it knowledge: how to approach a task with the tools it already has. Many agents use both.
How can my agent test my Android app?
Robomori lets coding agents create, start and control Android emulators and devices from one command, so they can install your app, take screenshots and check dark mode, font sizes and languages.
Instructions to make or update an app's UI so that it adapts to different Android devices including phones, tablets, foldables, laptops, desktop, TV, Auto, and XR. It includes how to handle different window sizes, pointing devices (such as mouse) and text entry devices (such as keyboard) using the Compose MediaQuery API, and how to preserve UI, navigation, scroll, and media playback state across configuration changes (such as folding/unfolding a foldable, rotating a device, or resizing a window). It also covers multi-pane layouts using Navigation3 Scenes, adaptive UI components (such as buttons) with varying target sizes, and adaptive layouts (including navigation areas - nav rails and nav bars) using the Compose Grid and FlexBox APIs. It also covers desktop experiences with keyboard shortcuts, tooltips and custom cursors.
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.
Adds inking and freehand drawing capabilities to an Android app using Jetpack Ink (androidx.ink) and Compose. Use this skill when implementing stylus or touch drawing surfaces, rendering wet and dry ink strokes, configuring stock brushes (pressure pen, marker, highlighter), implementing geometry-based erasing, linear undo and redo history, or stroke persistence with Room. Delivers working Compose and ViewModel implementations. Don't use for View-based (XML) inking or programmatic custom BrushFamily creation. For custom BrushFamily creation, custom tip shapes, or behavior node graphs, suggest the ink-custom-brush-builder skill.
Creates custom BrushFamily definitions for an Android app using Jetpack Ink (androidx.ink 1.1.0-alpha03 and higher). Use this skill when configuring custom BrushTip shapes, adding pressure, tilt, speed, or noise sensitivity using BrushBehavior node graphs, creating multi-coat layered brushes, applying tiling or particle stamping textures, configuring SlidingWindowModel input smoothing, or serializing brushes. Delivers complete Kotlin BrushFamily, BrushCoat, BrushTip, BrushPaint, and BrushBehavior implementations. Don't use for View-based (XML) inking, Compose drawing surface setup, or stock brush selection. For Compose drawing surface setup, InProgressStrokes wet and dry rendering, eraser, or persistence, suggest the ink-app-builder skill.
