Agent skill

Nuxt Best Practices

by vinayakkulkarni in vinayakkulkarni/nxui

Nuxt 4 performance optimization and architecture guidelines (current through Nuxt 4.5) for building fast, maintainable full-stack applications.

MITAuto-check passedDevelopment

Install Nuxt Best Practices

skills CLI

$ npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install vinayakkulkarni/nxui nuxt-best-practices --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/vinayakkulkarni/nxui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nuxt-best-practices .claude/skills/nuxt-best-practices && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "nuxt-best-practices" agent skill from https://github.com/vinayakkulkarni/nxui/tree/main/.agents/skills/nuxt-best-practices into .claude/skills/nuxt-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nuxt-best-practices", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/vinayakkulkarni/nxui/tree/main/.agents/skills/nuxt-best-practices

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install vinayakkulkarni/nxui nuxt-best-practices --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vinayakkulkarni/nxui.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/nuxt-best-practices .agents/skills/nuxt-best-practices && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "nuxt-best-practices" agent skill from https://github.com/vinayakkulkarni/nxui/tree/main/.agents/skills/nuxt-best-practices into .agents/skills/nuxt-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nuxt-best-practices", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install vinayakkulkarni/nxui nuxt-best-practices --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vinayakkulkarni/nxui.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/nuxt-best-practices .cursor/skills/nuxt-best-practices && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "nuxt-best-practices" agent skill from https://github.com/vinayakkulkarni/nxui/tree/main/.agents/skills/nuxt-best-practices into .cursor/skills/nuxt-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nuxt-best-practices", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/vinayakkulkarni/nxui.git --path .agents/skills/nuxt-best-practices

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install vinayakkulkarni/nxui nuxt-best-practices --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vinayakkulkarni/nxui.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/nuxt-best-practices .gemini/skills/nuxt-best-practices && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "nuxt-best-practices" agent skill from https://github.com/vinayakkulkarni/nxui/tree/main/.agents/skills/nuxt-best-practices into .gemini/skills/nuxt-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nuxt-best-practices", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install vinayakkulkarni/nxui nuxt-best-practices

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/vinayakkulkarni/nxui.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/nuxt-best-practices .github/skills/nuxt-best-practices && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "nuxt-best-practices" agent skill from https://github.com/vinayakkulkarni/nxui/tree/main/.agents/skills/nuxt-best-practices into .github/skills/nuxt-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nuxt-best-practices", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install vinayakkulkarni/nxui nuxt-best-practices --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vinayakkulkarni/nxui.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/nuxt-best-practices .opencode/skills/nuxt-best-practices && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "nuxt-best-practices" agent skill from https://github.com/vinayakkulkarni/nxui/tree/main/.agents/skills/nuxt-best-practices into .opencode/skills/nuxt-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nuxt-best-practices", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: nuxt-best-practices
GitHub stars: 212
Token cost: ~1.5k tokens
SKILL.md length: 534 words
Files: 31 (incl. scripts)
Skills in repo: 6
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Nuxt 4 performance optimization and architecture guidelines (current through Nuxt 4.5) for building fast, maintainable full-stack applications.

Works in 9 steps: Data Fetching (CRITICAL) → Auto-Imports & Organization (CRITICAL) → Server & API Routes (HIGH) → …
Tasks involving data fetching
SKILL.md covers When to Apply, Rule Categories by Priority, Quick Reference and How to Use, plus 1 more section
Rendering modes

What it does

Nuxt Best Practices is an agent skill from vinayakkulkarni/nxui. Nuxt 4 performance optimization and architecture guidelines (current through Nuxt 4.5) for building fast, maintainable full-stack applications. This skill should be used when writing, reviewing, or refactoring Nuxt code to ensure optimal patterns. Triggers on tasks involving data fetching, server routes, auto-imports, rendering modes, layouts, named views, or Nuxt-specific features.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 31 other files, including scripts (for example `AGENTS.md`, `package.json` and `rules/_sections.md`).

It sits in Development, covering Performance optimization and Refactoring. It works with Nuxt. The repository describes itself as: Beautiful animated components for Vue. Built with Tailwind CSS and motion-v. The licence is MIT.

When your agent uses it

Tasks involving data fetching
Rendering modes
Nuxt-specific features

Example prompts

“/nuxt-best-practices”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

Data Fetching (CRITICAL)
Auto-Imports & Organization (CRITICAL)
Server & API Routes (HIGH)
Rendering Modes (HIGH)
State Management (MEDIUM-HIGH)
Pages, Layouts & Navigation (MEDIUM)
Type Safety (MEDIUM)
Modules & Plugins (LOW-MEDIUM)
Performance & Deployment (LOW)

What it can do on your machine

Read from SKILL.md and the folder at commit 46001b5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nuxt Best Practices loads about 1.5k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~101
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from vinayakkulkarni/nxui at commit 46001b5, republished under its MIT licence (© vinayakkulkarni). 534 words, ~1,478 tokens.

Download SKILL.mdSave it as .claude/skills/nuxt-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 30 other files; get the full folder from GitHub.

name: nuxt-best-practices
description: Nuxt 4 performance optimization and architecture guidelines (current through Nuxt 4.5) for building fast, maintainable full-stack applications. This skill should be used when writing, reviewing, or refactoring Nuxt code to ensure optimal patterns. Triggers on tasks involving data fetching, server routes, auto-imports, rendering modes, layouts, named views, or Nuxt-specific features.
license: MIT
metadata.author: vinayakkulkarni
metadata.version: 1.0.0

Nuxt Best Practices

Comprehensive performance optimization guide for Nuxt 4 applications (current: Nuxt 4.5, with notes for 3.x apps approaching EOL). Contains 23 rules across 9 categories, prioritized by impact to guide automated refactoring and code generation.

When to Apply

Reference these guidelines when:

Writing new Nuxt pages, components, or composables
Implementing data fetching (useFetch, useAsyncData, the 4.5 enabled option)
Creating server routes and API endpoints
Organizing types, composables, and auto-imports
Working with Nuxt modules and plugins
Configuring rendering modes (SSR, SSG, SPA, 4.5 experimental SSR streaming)
Using layouts, named views, and NuxtLink prefetching (Nuxt 4.5 conventions)

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Data Fetching	CRITICAL	`data-`
2	Auto-Imports & Organization	CRITICAL	`imports-`
3	Server & API Routes	HIGH	`server-`
4	Rendering Modes	HIGH	`rendering-`
5	State Management	MEDIUM-HIGH	`state-`
6	Pages, Layouts & Navigation	MEDIUM	`pages-`
7	Type Safety	MEDIUM	`types-`
8	Modules & Plugins	LOW-MEDIUM	`modules-`
9	Performance & Deployment	LOW	`perf-`

Quick Reference

1. Data Fetching (CRITICAL)

data-use-fetch - Use useFetch/useAsyncData, never raw fetch in components
data-key-unique - Always provide unique keys for data fetching
data-lazy-loading - Use lazy option for non-critical data
data-transform - Transform data at fetch time, not in template
data-error-handling - Always handle error and pending states
data-refresh-patterns - Use refresh() and clear() appropriately
data-conditional-enabled - Use the enabled option for conditional fetching (4.5+)

2. Auto-Imports & Organization (CRITICAL)

imports-no-barrel-autoimport - Never create barrel exports in auto-imported directories
imports-component-naming - Don't duplicate folder prefix in component names
imports-type-locations - Place types in dedicated directories (app/types, shared/types, server/types)
imports-composable-exports - Composables export functions only, not types
imports-direct-composable-imports - Use direct imports between composables

3. Server & API Routes (HIGH)

server-validated-input - Use getValidatedQuery/readValidatedBody with Zod
server-route-meta - Always add defineRouteMeta for OpenAPI docs
server-runtime-config - Use useRuntimeConfig, never process.env
server-error-handling - Use createError for consistent error responses
server-middleware-order - Understand middleware execution order

4. Rendering Modes (HIGH)

rendering-route-rules - Configure rendering per-route with routeRules
rendering-hybrid - Use hybrid rendering for optimal performance
rendering-prerender - Prerender static pages at build time
rendering-client-only - Use ClientOnly for browser-specific components
rendering-ssr-streaming - Understand SSR streaming before enabling it (4.5+, experimental)

Show full SKILL.md (207 more words)Show less

5. State Management (MEDIUM-HIGH)

state-use-state - Use useState for SSR-safe shared state
state-pinia-setup - Set up Pinia correctly with Nuxt
state-hydration - Handle hydration mismatches properly
state-computed-over-watch - Prefer computed over watch for derived state

pages-use-layout - Use useLayout to read the resolved layout (4.5+)
pages-named-views - Use the name@view.vue convention for named views (4.5+)
pages-nuxtlink-custom-prefetch - Wire prefetch manually in NuxtLink custom slots (4.5+)

7. Type Safety (MEDIUM)

types-no-inline - Never define types inline in components/composables
types-import-paths - Use correct import paths (#shared, ~/, ~~/)
types-no-any - Never use any type
types-zod-schemas - Use Zod for runtime validation with type inference
types-strict-emits - Type emits fully; declare camelCase, listen kebab-case

8. Modules & Plugins (LOW-MEDIUM)

modules-order - Module order matters in nuxt.config
modules-runtime-vs-build - Understand runtime vs build-time modules
plugins-client-server - Use .client.ts and .server.ts suffixes correctly
plugins-provide-inject - Use provide/inject for cross-cutting concerns

9. Performance & Deployment (LOW)

perf-bundle-analysis - Analyze and optimize bundle size
perf-image-optimization - Use nuxt/image for optimized images
perf-font-loading - Configure font loading strategy
perf-caching-headers - Set appropriate cache headers

How to Use

Read individual rule files for detailed explanations and code examples:

rules/data-use-fetch.md
rules/imports-no-barrel-autoimport.md
rules/_sections.md

Each rule file contains:

Brief explanation of why it matters
Incorrect code example with explanation
Correct code example with explanation
Additional context and Nuxt-specific notes

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

Files

SKILL.md and 30 other files (scripts) in .agents/skills/nuxt-best-practices of vinayakkulkarni/nxui.

SKILL.md
AGENTS.md
package.json
rules/_sections.md
rules/_template.md
rules/data-conditional-enabled.md
rules/data-error-handling.md
rules/data-key-unique.md
rules/data-transform.md
rules/data-use-fetch.md
rules/imports-component-naming.md
rules/imports-composable-exports.md
rules/imports-direct-composable-imports.md
rules/imports-no-barrel-autoimport.md
rules/imports-type-locations.md
rules/pages-named-views.md
rules/pages-nuxtlink-custom-prefetch.md
rules/pages-use-layout.md
rules/rendering-client-only.md
rules/rendering-ssr-streaming.md
… and 11 more

Open the folder on GitHubat commit 46001b5

Compare with similar skills

Nuxt Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nuxt Best Practices compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Nuxt Best Practices this skillvinayakkulkarni/nxui	212	—	~1.5k	Automated safety check: Pass	MIT	2 days ago
Svelte5 Best PracticesSikandarJODD/cnblocks	431	1 repos	~810	Automated safety check: Pass	MIT	3 mo ago
React Best Practicesshapeshift/web	206	1 repos	~2k	Automated safety check: Pass	MIT	yesterday
Swift Concurrencysupabitapp/supaterm	172	—	~3.3k	Automated safety check: Pass	Custom licence	16 days ago
Swift ConcurrencyAFK-surf/OpenBridge	430	—	~2.8k	Automated safety check: Pass	MIT	4 mo ago
Handsontable Refactoring Ruleshandsontable/handsontable	22k	—	~815	Automated safety check: Pass	Custom licence	yesterday

Similar skills

Svelte5 Best Practices
SikandarJODD/cnblocks
Svelte 5 runes, snippets, SvelteKit patterns, and modern best practices for TypeScript and component development.
431 GitHub starsUsed in 1 repo~810 tokens
DevelopmentAuto-check passed
React Best Practices
shapeshift/web
Comprehensive React and Next.js performance optimization guide with 40+ rules for eliminating waterfalls, optimizing bundles, and improving rendering.
206 GitHub starsUsed in 1 repo~2k tokens
DevelopmentAuto-check passed
Swift Concurrency
supabitapp/supaterm
Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, and guide Swift 6 migration.
172 GitHub stars~3.3k tokensUpdated 16 days ago
DevelopmentAuto-check passed
Swift Concurrency
AFK-surf/OpenBridge
Expert guidance on Swift Concurrency best practices, patterns, and implementation.
430 GitHub stars~2.8k tokensUpdated 4 mo ago
DevelopmentAuto-check passed
Handsontable Refactoring Rules
handsontable/handsontable
Refactoring rules for Handsontable code: SOLID applied to plugins, Law of Demeter fixes, performance patterns and strict protection of backward compatibility.
22k GitHub stars~815 tokensUpdated yesterday
DevelopmentAuto-check passed
React Performance
affaan-m/ECC
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills).
277k GitHub starsUsed in 1 repo~4.5k tokens
DevelopmentAuto-check passed

Questions about Nuxt Best Practices

What does Nuxt Best Practices do?

Nuxt 4 performance optimization and architecture guidelines (current through Nuxt 4.5) for building fast, maintainable full-stack applications. Nuxt Best Practices is an agent skill from vinayakkulkarni/nxui.5) for building fast, maintainable full-stack applications.

When should I use Nuxt Best Practices?

Nuxt Best Practices fits situations like: tasks involving data fetching; rendering modes; nuxt-specific features.

How do I install Nuxt Best Practices in Claude Code?

Run `npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a claude-code`. Or copy the skill folder (.agents/skills/nuxt-best-practices in vinayakkulkarni/nxui) into .claude/skills/nuxt-best-practices in your project. Claude Code loads it when a task matches its description.

How do I install Nuxt Best Practices in Codex?

Run `npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a codex`. Or copy the skill folder (.agents/skills/nuxt-best-practices in vinayakkulkarni/nxui) into .agents/skills/nuxt-best-practices in your project. Codex loads it when a task matches its description.

Can I use Nuxt Best Practices in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vinayakkulkarni/nxui --skill nuxt-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nuxt-best-practices, .gemini/skills/nuxt-best-practices, .github/skills/nuxt-best-practices and .opencode/skills/nuxt-best-practices in your project.

What does Nuxt Best Practices need to run?

SKILL.md names no scripts, command-line tools or credentials: Nuxt Best Practices is instructions for the agent only.

Does Nuxt Best Practices access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nuxt Best Practices safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Nuxt Best Practices use?

Nuxt Best Practices is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nuxt Best Practices use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nuxt Best Practices?

Skills that share tags, products or a category with Nuxt Best Practices: Svelte5 Best Practices (SikandarJODD/cnblocks, 431 stars), React Best Practices (shapeshift/web, 206 stars), Swift Concurrency (supabitapp/supaterm, 172 stars) and Swift Concurrency (AFK-surf/OpenBridge, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nuxt Best Practices?

vinayakkulkarni (a GitHub user) maintains it in vinayakkulkarni/nxui, which has 212 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

Source: vinayakkulkarni/nxui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Nuxt Best Practices

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Nuxt Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Data Fetching (CRITICAL)

2. Auto-Imports & Organization (CRITICAL)

3. Server & API Routes (HIGH)

4. Rendering Modes (HIGH)

5. State Management (MEDIUM-HIGH)

6. Pages, Layouts & Navigation (MEDIUM)

7. Type Safety (MEDIUM)

8. Modules & Plugins (LOW-MEDIUM)

9. Performance & Deployment (LOW)

How to Use

Full Compiled Document

Files

Compare with similar skills

Similar skills

More from vinayakkulkarni/nxui

Related

Questions about Nuxt Best Practices