android-compose-xml-interoperability
Bridge Compose and the View system safely during incremental migrations, interoperability screens, and shared theming.
Works with
--- name: android-compose-xml-interoperability description: Bridge Compose and the View system safely during incremental migrations, interoperability screens, and shared theming. license: MIT --- # Android Compose XML Interoperability ## When To Use - Use this skill when the request is about: compose in fragment, androidview in compose, incremental compose migration. - Primary outcome: Bridge Compose and the View system safely during incremental migrations, interoperability screens, and shared theming. - Handoff skills when the scope expands: - `android-viewsystem-foundations` - `android-compose-foundations` ## Workflow 1. Identify whether the target surface is Compose, View system, or a mixed interoperability screen. 2. Select the lowest-friction UI pattern that satisfies responsiveness, accessibility, and performance needs. 3. Build the UI around stable state, explicit side effects, and reusable design tokens. 4. Exercise edge cases such as long text, font scaling, RTL, and narrow devices in the fixture apps. 5. Validate with unit, UI, and screenshot-friendly checks before handing off. ## Guardrails - Optimize for stable state and predictable rendering before adding animation or abstraction. - Respect accessibility semantics, contrast, focus order, and touch target guidance by default. - Do not mix Compose and View system ownership without an explicit interoperability boundary. - Prefer measured performance work over premature micro-optimizations. ## Anti-Patterns - Embedding navigation or business logic directly in leaf UI components. - Using fixed dimensions that break on localization or dynamic text. - Ignoring semantics and announcing only visual changes. - Porting XML patterns directly into Compose without adapting the mental model. ## Examples ### Happy path - Scenario: Embed a Compose task summary inside the XML fixture without ownership confusion. - Command: `cd examples/orbittasks-xml && ./gradlew :app:assembleDebug` ### Edge case - Scenario: Host a View-based screen from a Compose entry point during phased migration. - Command: `cd examples/orbittasks-compose && ./gradlew :app:assembleDebug` ### Failure recovery - Scenario: Separate interoperability prompts from pure View or pure Compose requests. - Command: `python3 scripts/eval_triggers.py --skill android-compose-xml-interoperability` ## 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/develop/ui/compose/migrate/interoperability-apis](https://developer.android.com/develop/ui/compose/migrate/interoperability-apis) - [https://developer.android.com/develop/ui/compose/migrate/strategy](https://developer.android.com/develop/ui/compose/migrate/strategy) - [https://developer.android.com/develop/ui/compose/migrate/other-considerations](https://developer.android.com/develop/ui/compose/migrate/other-considerations) - [https://developer.android.com/guide/fragments/communicate](https://developer.android.com/guide/fragments/communicate)
More Mobile skills
animation-vocabulary
emilkowalski/skills
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
developing-genkit-dart
firebase/agent-skills
Generates code and provides documentation for the Genkit Dart SDK. Use when the user asks to build AI agents in Dart, use Genkit flows, or integrate LLMs into Dart/Flutter applications.
