PluginBench
Skill
Pass
Audit score 90

nuxt-studio

onmax/nuxt-skills

Configure and operate self-hosted Nuxt Studio editor for Nuxt Content projects.

What is nuxt-studio?

Nuxt Studio is a self-hosted content editor for Nuxt Content that handles editing, publishing, and Git workflows. Use it when setting up the editor, customizing authentication, managing media and drafts, or deploying to production.

  • Configure OAuth and custom authentication providers for editor access
  • Manage visual and MDC editing with schema forms and draft content
  • Publish changes via Git to configured branches with conflict resolution
  • Handle media uploads and AI-assisted content editing
  • Deploy to SSR-capable environments with automated rebuild integration
  • Support monorepo and multi-branch publishing strategies

How to install nuxt-studio

npx skills add https://github.com/onmax/nuxt-skills --skill nuxt-studio
Prerequisites
  • Nuxt project with @nuxt/content module installed
  • Git repository (GitHub, GitLab, or other supported provider)
  • OAuth credentials or custom authentication setup for your provider
  • Node.js and npm/yarn for module installation
Claude Code
Cursor
Windsurf
Cline

How to use nuxt-studio

  1. 1.Run `npx nuxt module add nuxt-studio` to install the module
  2. 2.Configure repository settings (provider, owner, repo, branch) in `nuxt.config.ts`
  3. 3.Set authentication environment variables (e.g., `NUXT_STUDIO_AUTH_GITHUB_CLIENT_ID`)
  4. 4.Access the editor at `/_studio` route on your deployment
  5. 5.Verify local editing works against the filesystem, then test production login and one publish cycle

Use cases

Good for
  • Setting up a self-hosted content editor for a Nuxt Content site with GitHub authentication
  • Customizing editor filters and environment variables for team workflows
  • Publishing drafted content through Git with branch strategy management
  • Deploying Nuxt Studio to production with SSR and automated publishing
  • Integrating media management and schema-based forms into content workflows
Who it's for
  • Nuxt developers managing content-heavy sites
  • Teams needing self-hosted content editing without external services
  • Content editors using visual/MDC editing with schema validation
  • DevOps engineers deploying Nuxt Studio to production environments

nuxt-studio FAQ

What is the difference between Nuxt Studio and Nuxt Content?

Nuxt Studio owns content editing and publishing workflows. Nuxt Content owns collections, queries, parsing, and rendering. Keep collection and schema changes within the Nuxt Content boundary.

Where does Studio run by default?

Studio runs at the `/_studio` route by default on your Nuxt application.

How do I authenticate users in Nuxt Studio?

Configure OAuth (GitHub, GitLab, etc.) or custom authentication via environment variables. Authentication credentials must be set as deployment secrets.

Can I use Nuxt Studio with monorepos?

Yes, Nuxt Studio supports monorepo deployments and multi-branch publishing strategies as documented in the Deployment guide.

What deployment types does Nuxt Studio support?

Nuxt Studio requires SSR-capable deployments. Supported CI providers can infer repository metadata automatically.

Full instructions (SKILL.md)

Source of truth, from onmax/nuxt-skills.


name: nuxt-studio description: Configure and operate the self-hosted Nuxt Studio editor for Nuxt Content. Use when working with nuxt-studio installation, editor customization, OAuth or custom authentication, media, drafts, Git publishing, or production deployment. license: MIT

Nuxt Studio

Nuxt Studio owns content editing and publishing. Nuxt Content owns collections, queries, parsing, and rendering.

Workflow

  1. Inspect the installed nuxt-studio and @nuxt/content versions, deployment mode, repository provider, and authentication provider. Setup is understood when the editor route, Git target, and login callback all point at the same deployment.
  2. Open the smallest matching guide below and keep collection/schema changes within the nuxt-content boundary.
  3. Verify local editing against the filesystem, then verify production login and one publish cycle on an SSR-capable deployment. The work is complete when the commit reaches the configured branch and the rebuilt site exposes it.

Routing

TaskOpen
Install, repository settings, OAuth/custom auth, editor filters, or environment variablesConfiguration
Visual/MDC editing, schema forms, drafts, media, or AI assistanceLive editing
SSR deployment, Git publishing, branch strategy, conflicts, or monoreposDeployment
Collections, validators, queries, hooks, or renderingnuxt-content skill

Baseline

npx nuxt module add nuxt-studio
export default defineNuxtConfig({
  modules: ['@nuxt/content', 'nuxt-studio'],
  studio: {
    repository: {
      provider: 'github',
      owner: 'your-org',
      repo: 'your-repo',
      branch: 'main',
    },
  },
})
NUXT_STUDIO_AUTH_GITHUB_CLIENT_ID=<client-id>
NUXT_STUDIO_AUTH_GITHUB_CLIENT_SECRET=<client-secret>

Studio runs at /_studio by default. Supported CI providers can infer repository metadata, but authentication credentials remain explicit deployment secrets.