feat: add nuxt-claude-devtools module

[SemBystrov]

🔗 Linked issue

closes #1371

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

adds nuxt-claude-devtools module

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds two new YAML manifest files (modules/claude-devtools.yml and modules/nuxt-claude-devtools.yml) that provide structured metadata for a Nuxt DevTools integration named nuxt-claude-devtools / nuxt-claude-devtools (Claude Code). Each manifest includes name, description, repository and npm links, icon, website/learn_more, category/type, maintainers, and compatibility constraints for Nuxt and devtools. No executable code or API changes are introduced.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title clearly and concisely describes the main change: adding a new Nuxt module for claude-devtools integration.
Description check	✅ Passed	The description is related to the changeset, indicating it adds the nuxt-claude-devtools module as requested in the linked issue.
Linked Issues check	✅ Passed	The pull request adds two YAML manifest files that meet the objectives of issue #1371 by providing module metadata for nuxt-claude-devtools with proper Nuxt 4 compatibility specifications.
Out of Scope Changes check	✅ Passed	All changes are in scope: two manifest YAML files that define module metadata for nuxt-claude-devtools as required by issue #1371, with no extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@modules/nuxt-claude-devtools.yml`:
- Around line 14-16: This manifest is a stale duplicate; remove or consolidate
nuxt-claude-devtools.yml into the canonical claude-devtools.yml: delete the
duplicate nuxt-claude-devtools.yml file (or merge its minimal compatibility
block into claude-devtools.yml) and ensure the canonical manifest for package
`@oro.ad/nuxt-claude-devtools` contains the correct nuxt: ">=4.0.0" constraint and
any other metadata so there is a single up-to-date manifest.

🧹 Nitpick comments (1)

modules/nuxt-claude-devtools.yml (1)

5-8: Avoid empty-string metadata fields (icon/learn_more).

If these are unknown, omitting the keys (or using null) is usually safer than empty strings to avoid broken UI rendering or schema validation issues.

♻️ Suggested cleanup

-name: nuxt-claude-devtools
-description: Nuxt DevTools integration for Claude Code AI assistant
-repo: oro-ad/nuxt-claude-devtools
-npm: '@oro.ad/nuxt-claude-devtools'
-icon: ''
-github: https://github.com/oro-ad/nuxt-claude-devtools
-website: https://github.com/oro-ad/nuxt-claude-devtools
-learn_more: ''
+name: nuxt-claude-devtools
+description: Nuxt DevTools integration for Claude Code AI assistant
+repo: oro-ad/nuxt-claude-devtools
+npm: '@oro.ad/nuxt-claude-devtools'
+github: https://github.com/oro-ad/nuxt-claude-devtools
+website: https://github.com/oro-ad/nuxt-claude-devtools

[danielroe]

cool idea! (cc: @atinux @HugoRCD)

[HugoRCD]

Cool idea! (cc: @atinux @HugoRCD)

The idea is cool, but I don't know if it's really "useful" in the sense that I don't know if many people use the vscode available in the devtool or all the other embeds we've added to it? And especially if Claude updates the nuxt.config, the app will restart and kill the process, right?

[SemBystrov]

@danielroe @HugoRCD

Hi, thanks a lot for the kind words and for appreciating the idea — I really appreciate it

Regarding some of the current limitations: you’re absolutely right, they do exist at the moment. I’m still thinking about how to make the module more resilient from a UX perspective and in terms of deeper integration with Nuxt itself.

That said, I believe the benefits it brings are quite powerful:

First, it helps organize Claude Code documentation and configuration across a frontend team. This already makes collaboration and knowledge sharing much clearer. Support for Claude Code plugins naturally fits into this direction, and I’m planning to add it soon.

I’m also actively improving how Nuxt context is provided — for example, there’s already a component selector that allows applying changes by directly referencing the file in the prompt. Page-level context and additional runtime context are definitely on the roadmap as well.

Second, the module significantly lowers the friction around prototyping. It allows teams to iterate on ideas, UI changes, and small features much faster directly inside the Nuxt development flow, without constantly switching tools or losing context.

I’d be happy to continue the discussion around future directions, and once again — thank you for the feedback

[HugoRCD]

@danielroe @HugoRCD

Hi, thanks a lot for the kind words and for appreciating the idea — I really appreciate it

Regarding some of the current limitations: you’re absolutely right, they do exist at the moment. I’m still thinking about how to make the module more resilient from a UX perspective and in terms of deeper integration with Nuxt itself.

That said, I believe the benefits it brings are quite powerful:

First, it helps organize Claude Code documentation and configuration across a frontend team. This already makes collaboration and knowledge sharing much clearer. Support for Claude Code plugins naturally fits into this direction, and I’m planning to add it soon.

I’m also actively improving how Nuxt context is provided — for example, there’s already a component selector that allows applying changes by directly referencing the file in the prompt. Page-level context and additional runtime context are definitely on the roadmap as well.

Second, the module significantly lowers the friction around prototyping. It allows teams to iterate on ideas, UI changes, and small features much faster directly inside the Nuxt development flow, without constantly switching tools or losing context.

I’d be happy to continue the discussion around future directions, and once again — thank you for the feedback

Good defense 😆 Can't wait to see how far you'll get!