nuxt-best-practices
Nuxt 3/4 performance optimization and architecture guidelines 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, or Nuxt-specific features.
What this skill does
# Nuxt Best Practices Comprehensive performance optimization guide for Nuxt 3/4 applications. Contains 40+ rules across 8 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) - Creating server routes and API endpoints - Organizing types, composables, and auto-imports - Working with Nuxt modules and plugins - Configuring rendering modes (SSR, SSG, SPA) ## 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 | Type Safety | MEDIUM | `types-` | | 7 | Modules & Plugins | LOW-MEDIUM | `modules-` | | 8 | 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 ### 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 ### 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 ### 6. 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` - Use kebab-case emits with full type definitions ### 7. 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 ### 8. 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`
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.