jetpack-compose-skills MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

@Composable structure and state-hoisting discipline
Material 3 theming defaults
ViewModel + StateFlow + collectAsStateWithLifecycle patterns
Compose navigation (navigation-compose) conventions
Preview and test authoring that actually runs

Live-Demo

In der Praxis

jetpack-compose-skill.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "jetpack-compose-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/anhvt52/jetpack-compose-skills",
        "~/.claude/skills/jetpack-compose-skills"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "jetpack-compose-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/anhvt52/jetpack-compose-skills",
        "~/.claude/skills/jetpack-compose-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "jetpack-compose-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/anhvt52/jetpack-compose-skills",
        "~/.claude/skills/jetpack-compose-skills"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "jetpack-compose-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/anhvt52/jetpack-compose-skills",
        "~/.claude/skills/jetpack-compose-skills"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "jetpack-compose-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/anhvt52/jetpack-compose-skills",
        "~/.claude/skills/jetpack-compose-skills"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "jetpack-compose-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/anhvt52/jetpack-compose-skills",
          "~/.claude/skills/jetpack-compose-skills"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add jetpack-compose-skill -- git clone https://github.com/anhvt52/jetpack-compose-skills ~/.claude/skills/jetpack-compose-skills

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: jetpack-compose-skills

How to build a new Compose screen with state hoisting

👤 Android developers writing Compose UI ⏱ ~30 min intermediate

Wann einsetzen: New screen in a Compose app — get it right the first time rather than refactoring later.

Voraussetzungen

Android Studio with a recent Compose BOM — Use the latest stable Compose BOM in your build
Skill cloned — git clone https://github.com/anhvt52/jetpack-compose-skills ~/.claude/skills/jetpack-compose-skills

Ablauf

Describe the screen

Build a Profile screen: avatar, name, bio, follow button. State comes from a ProfileViewModel.✓ Kopiert

→ Stateless composable + stateful wrapper + preview
Wire the ViewModel

Hook up the ViewModel using collectAsStateWithLifecycle.✓ Kopiert

→ Lifecycle-aware state collection
Add a preview

Add @Preview variants for empty, loaded, and error states.✓ Kopiert

→ Three previews rendering without a live ViewModel

Ergebnis: A clean Compose screen with previews and a testable structure.

Fallstricke

Stateful composables you can't preview — Keep the composable stateless; hoist state to a wrapper
Wrong Modifier order — Skill prompts the order rule — padding before background for a padded background, etc.

Kombinieren mit: filesystem

Migrate a Views-based screen to Compose

👤 Teams converting legacy Android screens ⏱ ~90 min advanced

Wann einsetzen: You want to convert one screen at a time without rewriting the whole app.

Ablauf

Map the XML

Here's fragment_profile.xml. Map each widget to a Compose equivalent with notes on behaviors to preserve.✓ Kopiert

→ XML → Compose mapping with behavior notes
Rewrite

Produce the Compose screen. Keep state + actions identical to the Fragment.✓ Kopiert

→ Composable file + ViewModel untouched
Keep the navigation hybrid if needed

Swap only this screen, leave the rest on Fragments using ComposeView.✓ Kopiert

→ Hybrid navigation continues to work

Ergebnis: One screen cleanly ported without destabilizing the rest.

Fallstricke

Observer leaks when mixing with Fragment lifecycle — Use viewLifecycleOwner with ComposeView; release on destroy

Kombinieren mit: android

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

jetpack-compose-skill + android

Run the resulting screen in an emulator and iterate

Build the app, launch in the emulator, and show me the Profile screen.✓ Kopiert

jetpack-compose-skill + filesystem

Work across modules in a Compose project

Read feature/profile/ and add a Profile screen in ui/.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
compose-authoring	screen intent + state	Any new Compose UI
state-hoisting-review	existing composable	When a composable is hard to preview
view-to-compose-migration	XML + behaviors	Screen-by-screen migrations

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: none
Tokens pro Aufruf: 3–15k per screen
Kosten in €: free
Tipp: Scope to one screen + its ViewModel at a time

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: none at skill level

Datenabfluss: none

Fehlerbehebung

Häufige Fehler und Lösungen

Preview fails to render

Make composables stateless; drop the ViewModel from the preview path.

StateFlow not collecting on background

Use collectAsStateWithLifecycle, not collectAsState, on screens that may be backgrounded.

Alternativen

jetpack-compose-skills vs. andere

Alternative	Wann stattdessen	Kompromiss
apple-hig-designer-skill	You're on iOS SwiftUI instead of Android Compose	Different platform
claude-android-skill	You need broader Android help beyond UI	Less Compose-specific

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen