android-ui-states-validation
Review Android UI flows for empty, loading, error, offline, and edge-case behavior before release.
What this skill does
# 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-ui` only validates that design with assertions and screenshots. - Handoff skills when the scope expands: - `android-compose-accessibility` - `android-testing-ui` ## Workflow 1. Confirm the user-visible journey, target device behavior, and failure states that matter. 2. Build a state matrix that covers loading, content, empty, error, offline, stale-data, denied-permission, and post-action confirmation states as applicable. 3. Identify the owning screens, activities, destinations, and state holders for each branch of that matrix. 4. Validate recovery UX, accessibility, configuration changes, and back-stack behavior in the showcase apps. 5. 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 - [https://developer.android.com/topic/architecture/ui-layer](https://developer.android.com/topic/architecture/ui-layer) - [https://developer.android.com/guide/topics/resources/runtime-changes](https://developer.android.com/guide/topics/resources/runtime-changes) - [https://developer.android.com/guide/practices/ui_guidelines](https://developer.android.com/guide/practices/ui_guidelines) - [https://developer.android.com/guide/topics/ui/accessibility/apps](https://developer.android.com/guide/topics/ui/accessibility/apps)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.