claude-skills — Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

claude-skill-5.replay ▶ prêt

0/0

Installation

Dépôt de l’auteur · Documentation officielle des Skills Claude

Cas d'usage

Usages concrets : claude-skills

Ship a new Cloudflare-hosted React app in one session

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

Quand l'utiliser : You want Workers + Pages + D1 wired up without reading 5 Cloudflare docs.

Déroulement

Scaffold

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

→ 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.✓ Copié

→ Migration + Worker + React page
Deploy

Deploy to Cloudflare.✓ Copié

→ wrangler deploy output; URLs returned

Résultat : Live URL within an hour.

Pièges

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

Combiner avec : cloudflare · cloudflare-api

Migrate a Tailwind v3 project to v4

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

Quand l'utiliser : You want the new engine + CSS-first config without breaking everything.

Déroulement

Audit current

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

→ Change list with severity
Migrate config

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

→ New globals.css with @theme block
Fix utilities

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

→ Grep + rewrite pass

Résultat : Project on v4 without visual regressions.

Pièges

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

Combiner avec : filesystem

Wrap multiple AI providers behind one adapter

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

Quand l'utiliser : Locking into one provider feels wrong and you want a clean interface.

Déroulement

Define interface

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

→ Interface + 3 implementations
Wire up streaming

Add SSE streaming support to the adapter.✓ Copié

→ Streaming implementation consistent across providers

Résultat : A swappable AI layer.

Pièges

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

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

claude-skill-5 + cloudflare

Deploy + manage the CF resources the scaffold creates

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

claude-skill-5 + cloudflare-api

Bulk CF config operations

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

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
cf_scaffold	app type, features	New CF app
tailwind_migrate	v3 config	Tailwind upgrade
ai_adapter_scaffold	providers list	Multi-provider AI setup

Coût et limites

Coût d'exécution

Quota d'API: None in skill
Tokens par appel: Moderate
Monétaire: Cloudflare has a generous free tier; paid features as you grow
Astuce: Use wrangler dev locally; reserve cloud deploys for staging/prod.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : Wrangler handles CF auth; AI provider keys via env / CF secrets

Sortie de données : CF, AI providers you configure

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

Dépannage

Erreurs courantes et correctifs

D1 migration fails

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

Vérifier : 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

Vérifier : wrangler tail <worker>

Alternatives

claude-skills vs autres

Alternative	Quand l'utiliser	Compromis
Vercel / Next.js stack	You prefer Next ecosystem	Different deployment model, pricing
cc-frontend-skill	You care most about visual identity	Not stack-specific

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills