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

Warum nutzen

Hauptfunktionen

Expo SDK-aware scaffolding
expo-router file-based navigation patterns
EAS Build + Submit config guidance
TypeScript + Zustand defaults
Avoids RN-CLI era advice

Live-Demo

In der Praxis

skills-skill-7.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": {
    "skills-skill-7": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/zaferayan/skills",
        "~/.claude/skills/skills"
      ],
      "_inferred": true
    }
  }
}

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

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

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

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

VS Code → Cline → MCP Servers → Edit

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

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

~/.codeium/windsurf/mcp_config.json

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

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

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

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

claude mcp add skills-skill-7 -- git clone https://github.com/zaferayan/skills ~/.claude/skills/skills

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

Anwendungsfälle

Praxisnahe Nutzung: skills

Spin up a new Expo app with tabs and auth in one session

👤 Devs starting a new mobile app who want the boring parts done ⏱ ~45 min beginner

Wann einsetzen: Day zero of a new project — you want tabs, stack, and a sign-in flow without reading three blog posts.

Voraussetzungen

Node 20+, Xcode or Android Studio — Standard Expo requirements
Skill installed — git clone https://github.com/zaferayan/skills ~/.claude/skills/skills

Ablauf

Create the app

Use the Expo skill. Start a new app 'TaskFlow' with expo-router, TypeScript, and the tabs template. Include a login screen with email/password.✓ Kopiert

→ npx create-expo-app run, then file structure with app/(tabs)/ and app/(auth)/
Add state

Wire up Zustand for the auth store and persist to SecureStore.✓ Kopiert

→ stores/auth.ts with zustand + persist middleware using expo-secure-store
Test on device

Start the dev server and give me the QR code to scan.✓ Kopiert

→ npx expo start output

Ergebnis: A running app on your phone with tabs, auth, and persistence in under an hour.

Fallstricke

Claude suggests react-native-cli patterns — Explicitly say 'Expo SDK, expo-router only' in prompts

Kombinieren mit: filesystem

Configure EAS Build for iOS and Android

👤 Teams ready to ship TestFlight / Play internal ⏱ ~30 min intermediate

Wann einsetzen: First time submitting to TestFlight/Play.

Ablauf

Generate eas.json

Use the Expo skill. Generate eas.json with preview (internal) and production profiles, correct bundle identifier patterns, and env var injection.✓ Kopiert

→ Valid eas.json with both profiles
Wire secrets

Add my Sentry DSN and API base URL as EAS secrets for preview and production separately.✓ Kopiert

→ eas secret:create commands listed
Trigger the build

Now trigger a preview build for iOS.✓ Kopiert

→ eas build --profile preview --platform ios command

Ergebnis: EAS builds running, secrets managed.

Fallstricke

Committing app.json with secrets inline — Secrets go in EAS env, not app.json; let Claude use expo-constants to read them

Integrate a native module using Expo config plugins

👤 Devs adding functionality that requires native code (camera, biometrics, push) ⏱ ~20 min intermediate

Wann einsetzen: You need functionality beyond JS, but don't want to eject.

Ablauf

Identify the right package

Use the Expo skill. I need biometric auth. What's the right Expo SDK module and how do I configure it?✓ Kopiert

→ expo-local-authentication named with config plugin entries
Wire config plugin

Add the config plugin entries and required iOS usage strings.✓ Kopiert

→ app.json diff with plugins array and NSFaceIDUsageDescription

Ergebnis: Native module integrated via managed workflow.

Fallstricke

Adding raw native code and breaking managed workflow — Prefer Expo SDK modules and config plugins; eject only if truly needed

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

skills-skill-7 + filesystem

Bulk-apply Expo idioms across an existing RN project

Migrate my RN-CLI app to Expo managed workflow; point at the source tree.✓ Kopiert

skills-skill-7 + git

Commit each step separately so EAS setup changes are auditable

Commit the EAS config changes as a distinct commit before adding secrets.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
expo_scaffold	app name, template, features	Starting a new app
eas_config	profiles needed	Setting up builds
config_plugin_wire	native module name	Adding native features

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None built-in
Tokens pro Aufruf: Moderate
Kosten in €: Expo is free; EAS Build has a free tier with paid scaling
Tipp: Use EAS local builds during dev; cloud builds only for preview/prod.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No direct creds; EAS secrets are managed by Expo

Datenabfluss: None from skill itself

Never commit eas.json with inline secrets; use eas secret:create.
Treat expo-secure-store data as sensitive; it's encrypted but not invincible.

Fehlerbehebung

Häufige Fehler und Lösungen

Metro can't find module after install

Run npx expo install rather than npm install so SDK-compatible versions are picked

Prüfen: npx expo-doctor

Build fails with 'unrecognized bundle identifier'

Bundle ID mismatch between app.json and Apple Developer portal; align them

Native module not found at runtime

Config plugin didn't run; rebuild with eas build or npx expo prebuild --clean

Alternativen

skills vs. andere

Alternative	Wann stattdessen	Kompromiss
React Native CLI	You need maximum native control and don't mind managing Xcode/Gradle	Much more setup burden
Flutter	Cross-platform with Dart	Different language, different ecosystem

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen