android-viewsystem-foundations

name	android-viewsystem-foundations
description	Handle XML layouts, ConstraintLayout, Fragments, ViewBinding, DataBinding, and classic Android UI lifecycle patterns.
metadata	{"version":"0.1.0","category":"ui","tags":["android","xml","views","fragments"],"triggers":{"include":["xml layout android issue","fragment lifecycle android","constraintlayout cleanup","viewbinding databinding android","legacy view system screen"],"exclude":["compose-only side effects","retrofit serialization only","gradle wrapper bump"]},"owners":["@android-agent-skills/maintainers"],"test_targets":["examples/orbittasks-compose","examples/orbittasks-xml","benchmarks/triggers.jsonl"]}

Android ViewSystem Foundations

When To Use

• Use this skill when the request is about: xml layout android issue, fragment lifecycle android, constraintlayout cleanup.
• Primary outcome: Handle XML layouts, ConstraintLayout, Fragments, ViewBinding, DataBinding, and classic Android UI lifecycle patterns.
• Handoff skills when the scope expands:
• android-compose-xml-interoperability
• android-testing-ui

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: Refine the XML OrbitTasks screen with ViewBinding and explicit fragment-safe patterns.
• Command: cd examples/orbittasks-xml && ./gradlew :app:testDebugUnitTest

Edge case

• Scenario: Handle configuration changes, view lifecycle, and long content in classic layouts.
• Command: cd examples/orbittasks-xml && ./gradlew :app:connectedDebugAndroidTest

Failure recovery

• Scenario: Prevent XML or Fragment requests from being routed to Compose-first skills.
• Command: python3 scripts/eval_triggers.py --skill android-viewsystem-foundations

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/guide/fragments
• https://developer.android.com/topic/libraries/view-binding
• https://developer.android.com/training/constraint-layout
• https://developer.android.com/topic/libraries/data-binding