secondsky/claude-skills / plugins/nuxt-studio/skills/nuxt-studio
nuxt-studio
VerifiedThis skill should be used when the user asks to "set up Nuxt Studio", "configure Studio OAuth", "deploy Studio to Cloudflare", "add visual editor to Nuxt", "configure studio.domain.com subdomain", "Studio authentication", "Nuxt CMS", or mentions visual content editing, Nuxt Studio module, TipTap editor, Monaco editor, or content management for Nuxt websites.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.1 KB |
| references/cloudflare-deployment.md | markdown | 12.6 KB |
| references/editor-configuration.md | markdown | 15.0 KB |
| references/oauth-providers.md | markdown | 9.5 KB |
| references/subdomain-setup.md | markdown | 11.4 KB |
| references/troubleshooting.md | markdown | 17.7 KB |
| scripts/check-prerequisites.shexecutable | script | 8.0 KB |
| scripts/test-oauth.shexecutable | script | 6.8 KB |
| scripts/validate-config.shexecutable | script | 7.5 KB |
| templates/nuxt.config.ts | script | 4.4 KB |
| templates/studio-auth-github.ts | script | 6.0 KB |
| templates/studio-auth-gitlab.ts | script | 8.3 KB |
| templates/studio-auth-google.ts | script | 9.3 KB |
| templates/wrangler.toml | config | 4.4 KB |
templates/wrangler.toml
View on GitHub# Wrangler Configuration for Nuxt Studio on Cloudflare Workers
# Copy and customize for your Studio deployment
# Worker name (appears in Cloudflare dashboard)
name = "studio-cms"
# Entry point for the Worker
main = "./.output/server/index.mjs"
# Compatibility date - use latest stable
compatibility_date = "2025-12-25"
# Static assets configuration
[assets]
directory = "./.output/public"
# Custom subdomain routing
# Uncomment and customize for your domain
routes = [
{ pattern = "studio.yourdomain.com/*", zone_name = "yourdomain.com" }
]
# Alternative: Wildcard routing for preview branches
# routes = [
# { pattern = "*.studio.yourdomain.com/*", zone_name = "yourdomain.com" }
# ]
# Environment variables (non-sensitive only)
# Sensitive values should be set via `wrangler secret put` or Cloudflare dashboard
[vars]
NUXT_PUBLIC_STUDIO_URL = "https://studio.yourdomain.com"
# Example: Set Node.js compatibility flag if needed
# NODE_VERSION = "18"
# Production environment configuration
[env.production]
name = "studio-cms-production"
routes = [
{ pattern = "studio.yourdomain.com/*", zone_name = "yourdomain.com" }
]
[env.production.vars]
NUXT_PUBLIC_STUDIO_URL = "https://studio.yourdomain.com"
# Staging environment configuration
[env.staging]
name = "studio-cms-staging"
routes = [
{ pattern = "studio-staging.yourdomain.com/*", zone_name = "yourdomain.com" }
]
[env.staging.vars]
NUXT_PUBLIC_STUDIO_URL = "https://studio-staging.yourdomain.com"
# Development environment configuration
[env.development]
name = "studio-cms-dev"
routes = [
{ pattern = "studio-dev.yourdomain.com/*", zone_name = "yourdomain.com" }
]
[env.development.vars]
NUXT_PUBLIC_STUDIO_URL = "https://studio-dev.yourdomain.com"
# Durable Objects (if needed for advanced features)
# [[durable_objects.bindings]]
# name = "STUDIO_DO"
# class_name = "StudioDurableObject"
# script_name = "studio-cms"
# KV Namespaces (if needed for caching or session storage)
# [[kv_namespaces]]
# binding = "STUDIO_CACHE"
# id = "your_kv_namespace_id"
# preview_id = "your_preview_kv_namespace_id"
# R2 Buckets (if using R2 for media storage)
# [[r2_buckets]]
# binding = "STUDIO_MEDIA"
# bucket_name = "studio-media"
# preview_bucket_name = "studio-media-preview"
# D1 Databases (if needed for advanced Studio features)
# [[d1_databases]]
# binding = "STUDIO_DB"
# database_name = "studio-database"
# database_id = "your_database_id"
# Analytics Engine (for Studio usage analytics)
# [[analytics_engine_datasets]]
# binding = "STUDIO_ANALYTICS"
# Build configuration
[build]
# Build command (runs before deployment)
command = "npm run build"
# Watch paths for auto-rebuilding (development)
# watch_dirs = ["content/", "pages/", "components/"]
# Observability (optional - for monitoring)
# [observability]
# enabled = true
# Deployment configuration
[deploy]
# Compatibility flags (if needed for specific Workers features)
# compatibility_flags = []
# Limits (optional - adjust based on your needs)
# [limits]
# cpu_ms = 50
# memory_mb = 128
# Triggers (for scheduled tasks - if needed)
# [[triggers.crons]]
# cron = "0 0 * * *" # Daily at midnight
# name = "daily-cleanup"
# ====================================
# DEPLOYMENT INSTRUCTIONS
# ====================================
#
# 1. Install wrangler:
# npm install -g wrangler
# (or use bun: bun add -g wrangler)
#
# 2. Login to Cloudflare:
# wrangler login
#
# 3. Build your Nuxt app:
# npm run build
#
# 4. Set OAuth secrets (NEVER commit these):
# wrangler secret put NUXT_OAUTH_GITHUB_CLIENT_ID
# wrangler secret put NUXT_OAUTH_GITHUB_CLIENT_SECRET
# (repeat for GitLab/Google if using)
#
# 5. Deploy to production:
# wrangler deploy
#
# 6. Deploy to specific environment:
# wrangler deploy --env staging
# wrangler deploy --env development
#
# 7. View logs:
# wrangler tail
#
# 8. Test locally:
# wrangler dev
#
# ====================================
# SECURITY NOTES
# ====================================
#
# - NEVER commit OAuth secrets to Git
# - Use `wrangler secret` for all sensitive values
# - Keep this file in version control (safe without secrets)
# - Rotate secrets regularly
# - Use different OAuth apps for each environment
#
# ====================================
# CUSTOMIZATION
# ====================================
#
# Replace all instances of:
# - "yourdomain.com" with your actual domain
# - "studio-cms" with your preferred worker name
# - "studio.yourdomain.com" with your subdomain
#
# ====================================
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |