Nuxt Best Practices
ListedHelps with Nuxt, best practices as part of building frontend UIs and user experiences workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add vinayakkulkarni/vue-nuxt-best-practices --skill nuxt-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
vinayakkulkarni
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: vinayakkulkarni.dev.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
vinayakkulkarni.devundeclaredWhat it found
- skills/nuxt-best-practices/package.json:9contacts vinayakkulkarni.dev
"url": "https://vinayakkulkarni.dev"
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned vinayakkulkarni/vue-nuxt-best-practices at ba75969a5f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- ba75969a5f
- Scanned
- 31 files, 5,590 lines
About this skill
The nuxt-best-practices skill ensures AI agents adhere to the official Vue.js and Nuxt.js coding standards, optimizing application performance and maintainability. It automatically enforces strict linting rules, component structure guidelines, and build optimization strategies specific to the Nuxt ecosystem.
When to use it
- Generating new Nuxt components that strictly follow the recommended folder structure and naming conventions.
- Refactoring existing Vue codebases to align with Nuxt 3's latest architectural patterns and best practices.
- Ensuring AI-generated code passes standard linters like ESLint and Prettier without manual configuration adjustments.
- Optimizing build configurations for production deployments to reduce bundle size and improve load times.
Key capabilities
- Enforces strict adherence to Vue.js and Nuxt.js official documentation standards.
- Applies automated linting rules specific to the Nuxt ecosystem.
- Structures components according to best-practice architectural patterns.
- Optimizes build configurations for performance and scalability.
Example prompts
- "Generate a new dashboard component using Nuxt 3, ensuring it follows all official best practices for layout and state management."
- "Refactor this legacy Vue file into a modern Nuxt module, applying the latest coding standards and linting rules."
- "Optimize my current Nuxt build configuration to reduce bundle size while maintaining full functionality."
Tips & gotchas
Ensure your project is initialized with the latest version of Nuxt before applying these practices, as older versions may not support all enforced rules. This skill focuses on coding standards; it does not replace the need for manual performance testing in complex production environments.