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

Warum nutzen

Hauptfunktionen

Cloudflare Workers / D1 / R2 / Pages scaffolding
React 19 idioms (Server Components where applicable)
Tailwind v4 config + design tokens
AI integration adapters (multi-provider)
Production-ready — not tutorial sketches

Live-Demo

In der Praxis

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

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

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

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

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

VS Code → Cline → MCP Servers → Edit

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

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

~/.codeium/windsurf/mcp_config.json

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

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

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

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

claude mcp add claude-skill-5 -- git clone https://github.com/secondsky/claude-skills ~/.claude/skills/claude-skills

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

Anwendungsfälle

Praxisnahe Nutzung: claude-skills

Ship a new Cloudflare-hosted React app in one session

👤 Devs building on the CF stack ⏱ ~60 min intermediate

Wann einsetzen: You want Workers + Pages + D1 wired up without reading 5 Cloudflare docs.

Voraussetzungen

Cloudflare account + wrangler — npm i -g wrangler; wrangler login
Skill installed — git clone https://github.com/secondsky/claude-skills ~/.claude/skills/claude-skills

Ablauf

Scaffold

Use claude-skills. Scaffold a React 19 + Tailwind v4 app deployed to Cloudflare Pages with a Workers API and D1 DB.✓ Kopiert

→ Monorepo structure with apps/web, apps/api (Worker), wrangler.toml
Add a feature

Add a 'notes' feature — D1 schema, CRUD Worker endpoints, React UI with Tailwind v4 styling.✓ Kopiert

→ Migration + Worker + React page
Deploy

Deploy to Cloudflare.✓ Kopiert

→ wrangler deploy output; URLs returned

Ergebnis: Live URL within an hour.

Fallstricke

Wrangler config drift between environments — Use wrangler environments from the start — dev/staging/prod sections

Kombinieren mit: cloudflare · cloudflare-api

Migrate a Tailwind v3 project to v4

👤 Teams on v3 hitting the v4 release ⏱ ~45 min intermediate

Wann einsetzen: You want the new engine + CSS-first config without breaking everything.

Ablauf

Audit current

Use claude-skills. Audit my tailwind.config.js for v4 breaking changes.✓ Kopiert

→ Change list with severity
Migrate config

Convert to v4 CSS-first config with @theme directives.✓ Kopiert

→ New globals.css with @theme block
Fix utilities

Find v3 utilities that changed or were removed; rewrite usage.✓ Kopiert

→ Grep + rewrite pass

Ergebnis: Project on v4 without visual regressions.

Fallstricke

Plugin ecosystem not v4-ready yet — Check each plugin's v4 status; stay on v3 if a critical one lags

Kombinieren mit: filesystem

Wrap multiple AI providers behind one adapter

👤 Devs who want to swap Claude / GPT / local models without rewriting ⏱ ~45 min advanced

Wann einsetzen: Locking into one provider feels wrong and you want a clean interface.

Ablauf

Define interface

Use claude-skills ai-adapter pattern. Define a TS interface that abstracts chat completion across Claude, OpenAI, and a local model.✓ Kopiert

→ Interface + 3 implementations
Wire up streaming

Add SSE streaming support to the adapter.✓ Kopiert

→ Streaming implementation consistent across providers

Ergebnis: A swappable AI layer.

Fallstricke

Over-abstracting and losing provider-specific features — Keep a provider-specific escape hatch alongside the shared interface

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

claude-skill-5 + cloudflare

Deploy + manage the CF resources the scaffold creates

After scaffold, use cloudflare MCP to verify DNS and tail Worker logs.✓ Kopiert

claude-skill-5 + cloudflare-api

Bulk CF config operations

Configure cache rules and WAF for the deployed Pages project.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
cf_scaffold	app type, features	New CF app
tailwind_migrate	v3 config	Tailwind upgrade
ai_adapter_scaffold	providers list	Multi-provider AI setup

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None in skill
Tokens pro Aufruf: Moderate
Kosten in €: Cloudflare has a generous free tier; paid features as you grow
Tipp: Use wrangler dev locally; reserve cloud deploys for staging/prod.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: Wrangler handles CF auth; AI provider keys via env / CF secrets

Datenabfluss: CF, AI providers you configure

Use CF secrets (wrangler secret put) for API keys, never commit .dev.vars.

Fehlerbehebung

Häufige Fehler und Lösungen

D1 migration fails

Wrangler D1 migrations are finicky; run with --local first and inspect the SQL

Prüfen: wrangler d1 migrations list <db>

Tailwind v4 styles not applying

Check the @source directive captures your content paths

Deploy succeeds but Worker returns 500

wrangler tail to see the actual error

Prüfen: wrangler tail <worker>

Alternativen

claude-skills vs. andere

Alternative	Wann stattdessen	Kompromiss
Vercel / Next.js stack	You prefer Next ecosystem	Different deployment model, pricing
cc-frontend-skill	You care most about visual identity	Not stack-specific

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen