android-ux-flows
This skill is used to design Android user flows and screen structures that match the existing app patterns and keep forms, lists and navigation clear.
Best use case
android-ux-flows is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
This skill is used to design Android user flows and screen structures that match the existing app patterns and keep forms, lists and navigation clear.
Teams using android-ux-flows should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/android-ux-flows/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How android-ux-flows Compares
| Feature / Agent | android-ux-flows | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill is used to design Android user flows and screen structures that match the existing app patterns and keep forms, lists and navigation clear.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Android UX and Interaction Design Skill ## Purpose Turn a shaped product slice into a clear Android user journey and screen structure that feels natural in Compose, with simple navigation and discoverable actions. ## When to Use Use this skill after product shaping is complete and before any implementation work starts. ## Outputs - Entry → action → exit flow - Screen and section structure - Interaction rules, including tap areas and edit modes - Empty states and navigation hints ## Procedure 1. Identify where the user enters the flow (for example, app launch, list tap, notification tap) and where they leave it. 2. Decide which existing screens are reused and whether a new screen, bottom sheet or dialog is required. 3. For each screen: - Define sections and hierarchy (headers, “create new” area, list of existing items, secondary actions). - Separate “create” forms from “view/edit existing items”. 4. Specify interaction patterns that avoid everything being an inline form: - Use rows or cards for existing items. - Use a single “new item” form or dialog rather than repeating forms per row. - Put rename or advanced actions behind menus or explicit buttons. 5. Define empty states that explain what to do and how to reach the next screen. Include hints such as: - “Create a list, then tap it to view tasks.” 6. Ensure navigation is obvious: - Entire rows or cards as tap targets. - Icons or labels that signal navigation (for example chevrons). - No hidden navigation that relies on guessing. ## Guardrails - Do not invent new navigation paradigms. Use existing use of NavHost, top bars and bottom bars. - Do not turn lists into stacked edit forms. Keep clear separation between viewing and editing. - Do not specify colours or typography beyond hierarchy and grouping. - Respect existing screen names, terminology and style.
Related Skills
map-workflows-guide
Comprehensive guide for choosing the right MAP workflow based on task type and requirements
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
android-ui-design-guide
Apply Android/Jetpack Compose design principles following Material Design 3 when building any Android UI component. Only execute this when the current project is an Android project and involves UI-related work. Use this skill for Compose layouts, Material components, or Android app development. Ensures Material You compliance with Dynamic Color, expressive theming, 4dp grid spacing, Roboto typography with Type Scale, and native Android patterns. Prevents common anti-patterns like hardcoded colors, Dark Mode neglect, and touch target violations.
android-ui-compose
This skill is used to implement Android UI in Jetpack Compose based on an existing UX flow, focusing on clear hierarchy, list vs form separation and discoverable navigation.
android-jetpack-compose-expert
Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.
tdd-workflows-tdd-cycle
Use when working with tdd workflows tdd cycle
smart-workflows
SmartACE (Agentic Context Engineering) workflow engine with MCP-B (Master Client Bridge) and AMUM-QCI-ETHIC module. Dual database architecture using DuckDB (analytics) + SurrealDB (graph). Uses Blender 5.0 (bpy) and UE5 Remote Control. Use when (1) MCP-B agent-to-agent communication (INQC protocol), (2) AMUM 3→6→9 progressive alignment, (3) QCI quantum coherence states, (4) ETHIC principles enforcement (Marcel/Anthropic/EU AI Act), (5) SurrealDB graph relationships, (6) DuckDB SQL workflows, (7) ML inference with infera/vss, (8) Blender 5.0 headless processing, (9) UE5 scene control, (10) DuckLake time travel.
implementing-android-code
This skill should be used when implementing Android code in Bitwarden. Covers critical patterns, gotchas, and anti-patterns unique to this codebase. Triggered by "How do I implement a ViewModel?", "Create a new screen", "Add navigation", "Write a repository", "BaseViewModel pattern", "State-Action-Event", "type-safe navigation", "@Serializable route", "SavedStateHandle persistence", "process death recovery", "handleAction", "sendAction", "Hilt module", "Repository pattern", "implementing a screen", "adding a data source", "handling navigation", "encrypted storage", "security patterns", "Clock injection", "DataState", or any questions about implementing features, screens, ViewModels, data sources, or navigation in the Bitwarden Android app.
android-agent-skills
Production-ready Agent Skills framework for Android Kotlin development. Provides Clean Architecture patterns, Jetpack Compose best practices, validation DSL, MVI state management, error handling, and AI-powered code generation. Use when building Android apps with quality standards, generating ViewModels, Repositories, UseCases, Compose screens, or writing pure Kotlin Agent Skills.
airflow-workflows
Apache Airflow DAG design, operators, and scheduling best practices.
adaptive-workflows
Self-learning workflow system that tracks what works best for your use cases. Records experiment results, suggests optimizations, creates custom templates, and builds a personal knowledge base. Use to learn from experience and optimize your LLM workflows over time.
workflows-expert
Activate when requests involve workflow execution, CI/CD pipelines, git automation, or multi-step task orchestration. This skill provides workflows-mcp MCP server integration with tag-based workflow discovery, DAG-based execution, and variable syntax expertise. Trigger on phrases like "run workflow", "execute workflow", "orchestrate tasks", "automate CI/CD", or "workflow information".