/ Directory / Playground / claude-skills
← All servers ↗ GitHub
● Community secondsky ⚡ Instant

claude-skills

by secondsky · secondsky/claude-skills

Production-ready Claude Code skills for Cloudflare, React, Tailwind v4, and AI integrations — the modern full-stack bundle.

A focused set of skills for the Cloudflare + React + Tailwind v4 + AI stack. Opinionated toward what actually ships in 2026: Workers, D1, R2, Pages on Cloudflare; React 19 + Tailwind v4 on the frontend; provider-agnostic AI integration patterns.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

claude-skill-5.replay ▶ ready
0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use claude-skills

Ship a new Cloudflare-hosted React app in one session

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

When to use: You want Workers + Pages + D1 wired up without reading 5 Cloudflare docs.

Flow
  1. Scaffold
    Use claude-skills. Scaffold a React 19 + Tailwind v4 app deployed to Cloudflare Pages with a Workers API and D1 DB.✓ Copied
    → Monorepo structure with apps/web, apps/api (Worker), wrangler.toml
  2. Add a feature
    Add a 'notes' feature — D1 schema, CRUD Worker endpoints, React UI with Tailwind v4 styling.✓ Copied
    → Migration + Worker + React page
  3. Deploy
    Deploy to Cloudflare.✓ Copied
    → wrangler deploy output; URLs returned

Outcome: Live URL within an hour.

Pitfalls
  • Wrangler config drift between environments — Use wrangler environments from the start — dev/staging/prod sections
Combine with: cloudflare · cloudflare-api

Migrate a Tailwind v3 project to v4

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

When to use: You want the new engine + CSS-first config without breaking everything.

Flow
  1. Audit current
    Use claude-skills. Audit my tailwind.config.js for v4 breaking changes.✓ Copied
    → Change list with severity
  2. Migrate config
    Convert to v4 CSS-first config with @theme directives.✓ Copied
    → New globals.css with @theme block
  3. Fix utilities
    Find v3 utilities that changed or were removed; rewrite usage.✓ Copied
    → Grep + rewrite pass

Outcome: Project on v4 without visual regressions.

Pitfalls
  • Plugin ecosystem not v4-ready yet — Check each plugin's v4 status; stay on v3 if a critical one lags
Combine with: filesystem

Wrap multiple AI providers behind one adapter

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

When to use: Locking into one provider feels wrong and you want a clean interface.

Flow
  1. Define interface
    Use claude-skills ai-adapter pattern. Define a TS interface that abstracts chat completion across Claude, OpenAI, and a local model.✓ Copied
    → Interface + 3 implementations
  2. Wire up streaming
    Add SSE streaming support to the adapter.✓ Copied
    → Streaming implementation consistent across providers

Outcome: A swappable AI layer.

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

Combinations

Pair with other MCPs for X10 leverage

claude-skill-5 + cloudflare

Deploy + manage the CF resources the scaffold creates

After scaffold, use cloudflare MCP to verify DNS and tail Worker logs.✓ Copied
claude-skill-5 + cloudflare-api

Bulk CF config operations

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

Tools

What this MCP exposes

ToolInputsWhen to callCost
cf_scaffold app type, features New CF app 0
tailwind_migrate v3 config Tailwind upgrade 0
ai_adapter_scaffold providers list Multi-provider AI setup 0

Cost & Limits

What this costs to run

API quota
None in skill
Tokens per call
Moderate
Monetary
Cloudflare has a generous free tier; paid features as you grow
Tip
Use wrangler dev locally; reserve cloud deploys for staging/prod.

Security

Permissions, secrets, blast radius

Credential storage: Wrangler handles CF auth; AI provider keys via env / CF secrets
Data egress: CF, AI providers you configure

Troubleshooting

Common errors and fixes

D1 migration fails

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

Verify: 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

Verify: wrangler tail <worker>

Alternatives

claude-skills vs others

AlternativeWhen to use it insteadTradeoff
Vercel / Next.js stackYou prefer Next ecosystemDifferent deployment model, pricing
cc-frontend-skillYou care most about visual identityNot stack-specific

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Continue exploring

Related tools and workflows

Choose another guide for your workflow, or explore a collection.

Shared context · cloudflare

Cloudflare Skills

Apply Cloudflare’s agent skills to development on the Cloudflare platform.

Skill

Browse all topic collections → · See 29 new official additions →