claude-skills

왜 쓰나요

핵심 기능

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

라이브 데모

실제 사용 모습

claude-skill-5.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: claude-skills

Ship a new Cloudflare-hosted React app in one session

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

언제 쓸까: You want Workers + Pages + D1 wired up without reading 5 Cloudflare docs.

흐름

Scaffold

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

→ 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.✓ 복사됨

→ Migration + Worker + React page
Deploy

Deploy to Cloudflare.✓ 복사됨

→ wrangler deploy output; URLs returned

결과: Live URL within an hour.

함정

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

함께 쓰기: cloudflare · cloudflare-api

Migrate a Tailwind v3 project to v4

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

언제 쓸까: You want the new engine + CSS-first config without breaking everything.

흐름

Audit current

Use claude-skills. Audit my tailwind.config.js for v4 breaking changes.✓ 복사됨

→ Change list with severity
Migrate config

Convert to v4 CSS-first config with @theme directives.✓ 복사됨

→ New globals.css with @theme block
Fix utilities

Find v3 utilities that changed or were removed; rewrite usage.✓ 복사됨

→ Grep + rewrite pass

결과: Project on v4 without visual regressions.

함정

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

함께 쓰기: filesystem

Wrap multiple AI providers behind one adapter

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

언제 쓸까: Locking into one provider feels wrong and you want a clean interface.

흐름

Define interface

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

→ Interface + 3 implementations
Wire up streaming

Add SSE streaming support to the adapter.✓ 복사됨

→ Streaming implementation consistent across providers

결과: A swappable AI layer.

함정

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

조합

다른 MCP와 조합해 10배 효율

claude-skill-5 + cloudflare

Deploy + manage the CF resources the scaffold creates

After scaffold, use cloudflare MCP to verify DNS and tail Worker logs.✓ 복사됨

claude-skill-5 + cloudflare-api

Bulk CF config operations

Configure cache rules and WAF for the deployed Pages project.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
cf_scaffold	app type, features	New CF app
tailwind_migrate	v3 config	Tailwind upgrade
ai_adapter_scaffold	providers list	Multi-provider AI setup

비용 및 제한

운영 비용

API 쿼터: None in skill
호출당 토큰: Moderate
금액: Cloudflare has a generous free tier; paid features as you grow
팁: Use wrangler dev locally; reserve cloud deploys for staging/prod.

보안

권한, 시크릿, 파급범위

자격 증명 저장: Wrangler handles CF auth; AI provider keys via env / CF secrets

데이터 외부 송신: CF, AI providers you configure

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

문제 해결

자주 발생하는 오류와 해결

D1 migration fails

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

확인: 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

확인: wrangler tail <worker>

대안

claude-skills 다른 것과 비교

대안	언제 쓰나	단점/장점
Vercel / Next.js stack	You prefer Next ecosystem	Different deployment model, pricing
cc-frontend-skill	You care most about visual identity	Not stack-specific