Skip to content

nuxt-studio

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.

1,565
installs
0 up / 0 down, score 0.00
votes
724
repo stars
Updated
less than a month ago
In the catalog since
1 Oct 2026
From
onmax/nuxt-skills
Web & Frontend
Get it through your agent npx skills add onmax/nuxt-skills@nuxt-studio

Skill instructions

Rendered from the published SKILL.md, 46 lines.

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

Task Open
Install, repository settings, OAuth/custom auth, editor filters, or environment variables Configuration
Visual/MDC editing, schema forms, drafts, media, or AI assistance Live editing
SSR deployment, Git publishing, branch strategy, conflicts, or monorepos Deployment
Collections, validators, queries, hooks, or rendering nuxt-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.