nuxt-modules
Use when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables, plugins), (4) Server extensions (API routes, middleware), (5) Releasing/publishing modules to npm, (6) Setting up CI/CD workflows for modules. Provides defineNuxtModule patterns, Kit utilities, hooks, E2E testing, and release automation.
Security Assessment
About nuxt-modules
nuxt-modules is a development guide for building Nuxt modules that extend framework functionality. It covers the full lifecycle: published npm modules (the @nuxtjs/ and nuxt- families), local project modules in a modules/ directory, runtime extensions such as components, composables, and plugins, server extensions like API routes and middleware, and the release and publishing process including CI/CD workflow setup. Core building blocks include defineNuxtModule patterns, Nuxt Kit utilities, hooks, E2E testing, and release automation.
Getting started is scaffolded with npx nuxi init -t module my-module, followed by a playground dev server, a watch-mode build, and a test runner. The recommended project structure centers on a src/module.ts entry point and a src/runtime/ directory holding components, composables, plugins, and server code that gets injected into the user's app, alongside a playground/ for dev testing and test/fixtures/ for E2E tests.
The guidance is split across focused reference files that should be loaded only as needed: a development reference for module anatomy, defineNuxtModule, and Kit utilities; a testing-and-publishing reference for E2E tests, best practices, releasing, and npm publishing; and a CI-workflows reference with copy-paste CI/CD templates. The skill explicitly advises against loading all references at once, instead selecting the file relevant to the current task.
Use it when creating any kind of Nuxt module, whether a distributable npm package, a project-specific local extension, or a simple inline hook in nuxt.config.ts, or when setting up testing, releasing, or CI/CD for a module. It positions itself alongside related nuxt (basics) and vue (runtime patterns) skills, and links to the official Module Guide, Nuxt Kit docs, and module starter for deeper reference.
FAQ
What types of Nuxt modules does it cover?
Published npm modules, local project modules in a modules/ directory, and simple inline hooks in nuxt.config.ts, plus runtime and server extensions.
How do I scaffold a new module?
Run npx nuxi init -t module my-module, then use the provided scripts for the playground dev server, watch-mode build, and tests.
Where does runtime code that gets injected into the app live?
In the src/runtime/ directory, which holds components, composables, plugins, and server code, with src/module.ts as the entry point.
Should I load all the reference files?
No. The skill advises loading only the reference relevant to your task, whether development, testing-and-publishing, or ci-workflows, rather than all at once.
Does it help with publishing and CI/CD?
Yes. It includes a testing-and-publishing reference covering releasing and npm publishing, and a ci-workflows reference with copy-paste CI/CD templates.
Install nuxt-modules
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
onmax/nuxt-skills