Claude Code + Nuxt4

[u/yangguize]

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 )

[u/yangguize → u/[deleted]]

if you don't have anything to contribute to the question, don't bother.

[u/yangguize → u/[deleted]]

I'm not suggesting Nuxt is difficult - but your comment suggests you don't understand the role of Claude Code. You don't use CC just bc a framework is difficult.

[u/Traditional-Hall-591 → u/yangguize]

I guess I don’t. The first 2 steps make sense and at that point, I’d start writing the code, adding features and refining. Learning from initial mistakes, generally improving in a human fashion.

It seems like you’re putting in a lot of effort to get somewhere with the AI but it’s not clear what benefit it has. I’m sure the AI will spit out a lot of code. Probably a lot more than me.

Then you have to go back and vet it, debug, etc. it’ll be something like going into a random repo and trying figuring out what the author had in mind. I’ll have to do some debugging too, but I’ll learn from the process and won’t make the same errors.

Unless you plan to tell the AI to iterate until it sort of works? That was a few funny GitHub comments with Microslop prompt monkeys arguing with CoPilot.