About

Imported from krutikjain/android-agent-skills (skills/android-viewsystem-foundations/SKILL.md). Install upstream with npx skills add krutikjain/android-agent-skills --skill android-viewsystem-foundations. Copyright stays with the author.

Android ViewSystem Foundations

Name: android-viewsystem-foundations
Author: krutikjain

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.
Reach for this skill when the main surface is XML, Fragment, RecyclerView, or binding lifecycle work rather than Compose-first UI.
Handoff skills when the scope expands:
android-compose-xml-interoperability
android-testing-ui

Workflow

Identify whether the target surface is Fragment, Activity, custom view, RecyclerView, or a mixed Compose/View interoperability screen.
Anchor ownership correctly: view bindings to the view lifecycle, adapters to explicit item models, and navigation/transactions outside leaf views.
Fix layout and rendering issues with classic View tools first: ConstraintLayout, RecyclerView diffing, window insets, and binding-safe updates.
Exercise Fragment recreation, long text, font scaling, RTL, and process-lifecycle edges before considering the change complete.
Hand off Compose interoperability or UI test depth only after the View-system ownership model is stable.

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.
Clear ViewBinding references when the Fragment view is destroyed; do not keep view references alive past the view lifecycle.

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.
Holding Fragment view state in stale bindings, view references, or adapters across view recreation.

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

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/krutikjain-android-agent-skills-android-viewsystem-foundations/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

krutikjain-android-agent-skills-android-viewsystem-foundations.ocm.jsonjson

{
  "ocm": "1",
  "id": "krutikjain-android-agent-skills-android-viewsystem-foundations",
  "kind": "skill",
  "name": "android-viewsystem-foundations",
  "description": "Handle XML layouts, ConstraintLayout, Fragments, ViewBinding, DataBinding, and classic Android UI lifecycle patterns.",
  "publisher": "krutikjain",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "android",
      "xml",
      "views",
      "fragments",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Handle XML layouts, ConstraintLayout, Fragments, ViewBinding, DataBinding, and classic Android UI lifecycle patterns."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/krutikjain/android-agent-skills",
      "path": "skills/android-viewsystem-foundations/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/krutikjain/android-agent-skills/blob/HEAD/skills/android-viewsystem-foundations/SKILL.md",
      "key": "krutikjain/android-agent-skills/skills/android-viewsystem-foundations/SKILL.md"
    }
  },
  "instructions": "# Android ViewSystem Foundations\n\n## When To Use\n- Use this skill when the request is about: xml layout android issue, fragment lifecycle android, constraintlayout cleanup.\n- Primary outcome: Handle XML layouts, ConstraintLayout, Fragments, ViewBinding, DataBinding, and classic Android UI lifecycle patterns.\n- Reach for this skill when the main surface is XML, Fragment, RecyclerView, or binding lifecycle work rather than Compose-first UI.\n- Handoff skills when the scope expands:\n- `android-compose-xml-interoperability`\n- `android-testing-ui`\n\n## Workflow\n1. Identify whether the target surface ",
  "cost": {
    "context_tokens": 893
  }
}

Fetch it by URL: GET /api/v1/registry/krutikjain-android-agent-skills-android-viewsystem-foundations/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.