nuxt-studio▌
onmax/nuxt-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Self-hosted, open-source CMS module for editing Nuxt Content websites in production.
Nuxt Studio
Self-hosted, open-source CMS module for editing Nuxt Content websites in production.
When to Use
Working with:
- Installing and configuring
nuxt-studiomodule - Authentication providers (GitHub, GitLab, Google OAuth, SSO, custom)
- Git provider setup (GitHub, GitLab, branch config)
- Visual content editing (MDC components, YAML/JSON forms, frontmatter)
- Media management (public dir, NuxtHub blob, S3, R2)
- Publishing flow (draft layer, conflict detection, CI/CD rebuild)
- AI-powered content assistance (Vercel AI Gateway)
For content collections/queries: use nuxt-content skill
For NuxtHub storage/database: use nuxthub skill
For Nuxt basics: use nuxt skill
Available Guidance
Read specific files based on current work:
- references/configuration.md - Module setup, auth providers, Git providers, environment variables
- references/live-editing.md - Visual editor, media management, MDC components, AI features
- references/deployment.md - SSR requirements, Git publishing, branch strategies, CI/CD
Loading Files
Consider loading these reference files based on your task:
- references/configuration.md - if installing, configuring auth/git providers, or setting env vars
- references/live-editing.md - if working with content editor, media, components, or AI features
- references/deployment.md - if deploying, configuring branches, or troubleshooting publish flow
DO NOT load all files at once. Load only what's relevant to your current task.
Key Concepts
| Concept | Purpose |
|---|---|
| Auth providers | Control who can access Studio (GitHub, GitLab, Google, SSO) |
| Git providers | Handle publishing commits to your repository |
| Draft layer | IndexedDB-backed local storage for unpublished changes |
| Media manager | Upload/browse files in /public or external blob storage |
| Visual editor | TipTap-based WYSIWYG with MDC component support |
| Publishing | Commits drafts to Git, triggers CI/CD rebuild |
Quick Start
npx nuxt module add nuxt-studio
// nuxt.config.ts
export default defineNuxtConfig({
modules: ['@nuxt/content', 'nuxt-studio'],
studio: {
repository: {
provider: 'github',
owner: 'your-username',
repo: 'your-repo',
branch: 'main',
},
},
})
# .env
STUDIO_GITHUB_CLIENT_ID=<client_id>
STUDIO_GITHUB_CLIENT_SECRET=<client_secret>
Access Studio at https://your-site.com/_studio (default route).
Official Documentation
- Nuxt Studio: https://nuxt.studio
- Setup: https://nuxt.studio/setup
- GitHub: https://github.com/nuxt-content/nuxt-studio
Token Efficiency
Main skill: ~300 tokens. Each sub-file: ~800-1200 tokens. Only load files relevant to current task.
How to use nuxt-studio on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add nuxt-studio
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches nuxt-studio from GitHub repository onmax/nuxt-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate nuxt-studio. Access the skill through slash commands (e.g., /nuxt-studio) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★61 reviews- ★★★★★Benjamin Jackson· Dec 28, 2024
Useful defaults in nuxt-studio — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Evelyn Gonzalez· Dec 20, 2024
Keeps context tight: nuxt-studio is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Noor Garcia· Dec 20, 2024
Registry listing for nuxt-studio matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Pratham Ware· Dec 16, 2024
We added nuxt-studio from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Noor Wang· Dec 8, 2024
nuxt-studio is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Isabella Menon· Nov 27, 2024
Solid pick for teams standardizing on skills: nuxt-studio is focused, and the summary matches what you get after install.
- ★★★★★Emma Malhotra· Nov 19, 2024
nuxt-studio has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ishan Garcia· Nov 15, 2024
nuxt-studio has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Emma Jain· Nov 11, 2024
I recommend nuxt-studio for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Noor Liu· Nov 11, 2024
nuxt-studio reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 61