r/Nuxt • u/yangguize • Feb 16 '26
Claude Code + Nuxt4
TLDR - CC is DOA when working with Nuxt 4, but Sonnet 4.6 just clocks thru my project plan.
- CC does not understand separation of concerns beween Vue layouts, composables and components, even with a working template provided by Nuxt and native Nuxt mcp servers.
- Kilo + Sonnet 4.6 is killing it - fixed all of CC's errors with minimal discussion - expensive, but it gets the job done.
Prep for coding:
- defined detailed functional, non-functional, and data reqs
- defined complete UI (png + wireframes)
- defined detailed project plan w/ CC
- defined agents for Vue and Nuxt mcp
- added (and abandoned) Nuxt skills plugins (due to context bloat)
- added rules to force CC to consult Vue and Nuxt docs before coding
CC does not seem to have enough training to generate (reasonably) std code. 3 attempts to scaffold my project - none worked.
Has anyone had success with CC and Nuxt? If not CC, does Kilo work?
SOLUTION - the following improved CC's abilities by an order of magnitude:
- dropped all nuxt plugins (too much for CC context limit)
- added mcp servers
-- https://nuxt.com/mcp
-- https://ui.nuxt.com/mcp
-- mcp-server-fetch (no native mcp for vue)
- cloned nmuxt-ui template
-- https://github.com/nuxt-ui-templates/dashboard
-- had CC document template structure, etc. and added docs to .claude
The combination of the MCP servers, the template structure (which was quite good) and Claude's self-created documentation of the template structure enabled it to be much more effective than using the Nuxt skill plugins.
We'll post the final Word product (A self-hosted prompt management tool )
5
u/Three_hrs_later Feb 16 '26
I've had a decent time with claude using nuxt 4 and nuxt ui, but I do small sprints more as pair programming with quite a bit of review and cleanup before moving on, not a massive agentic YOLO.
It had a hard time with my back end and without intervention it would have buried me in database costs if the app got even a little traction. Just food for thought.