nuxt

A set of coding guidelines for Nuxt 3 and 4 applications, which are web projects built with Vue. It covers project structure, automatic imports, server components, data loading, application state, and styling.

In plain words
What is it for?
Use it when building or reviewing Nuxt applications, especially pages, components, server routes, data fetching, shared state, and authentication middleware.
Why use it?
It gives developers consistent patterns for organizing Nuxt code and loading data, helping avoid ad-hoc project structures and mismatched Vue practices.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/renvia-code/best-cursor-rules/nuxt
Clone the repo
git clone --depth 1 https://github.com/Renvia-code/best-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,079 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02079
Opus 5 $0.00000 $0.01040
Sonnet 5 $0.00000 $0.00416
Haiku 4.5 $0.00000 $0.00208

Measured yesterday against content hash c9e294ab7bc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nuxt scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/frameworks/nuxt.mdc · 416 lines

How it starts

The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Nuxt Best Practices

Overview

Aspect Recommendation
Version Nuxt 3.x / 4.x
Vue Vue 3 Composition API
Data Fetching useFetch / useAsyncData
State useState / Pinia
Styling Tailwind CSS or UnoCSS

Project Structure

app/                      # Nuxt 4 app directory
├── pages/
│   ├── index.vue
│   ├── about.vue
│   └── users/
│       ├── index.vue
│       └── [id].vue
├── components/
│   ├── AppHeader.vue
│   └── ui/
├── composables/
│   ├── useAuth.ts
│   └── useApi.ts
├── layouts/
│   ├── default.vue
│   └── auth.vue
├── middleware/
│   └── auth.ts
└── plugins/
server/
├── api/
│   └── users/
│       ├── index.get.ts
│       └── [id].get.ts
├── middleware/
└── utils/
public/
nuxt.config.ts

Data Fetching

useFetch (Recommended)

<script setup lang="ts">
// Basic fetch
const { data: posts, status } = await useFetch('/api/posts')

// With options
const { data: user, refresh, error } = await useFetch(`/api/users/${id}`, {
  query: { include: 'profile' },
  headers: { Authorization: `Bearer ${token}` },
  transform: (data) => data.user,
})

// POST request
const { data } = await useFetch('/api/users', {
  method: 'POST',
  body: { name: 'John', email: '[email protected]' },
})
</script>

<template>
  <div v-if="status === 'pending'">Loading...</div>
  <div v-else-if="error">Error: {{ error.message }}</div>
  <div v-else>{{ posts }}</div>
</template>

useAsyncData (For Complex Logic)

<script setup lang="ts">
const route = useRoute()

const { data, status, error } = await useAsyncData(
  `user-${route.params.id}`,
  async () => {
    const [user, posts] = await Promise.all([
      $fetch(`/api/users/${route.params.id}`),
      $fetch(`/api/users/${route.params.id}/posts`),
    ])
    return { user, posts }
  }
)
</script>

Lazy Fetching (Non-blocking)

<script setup lang="ts">
// Navigation happens immediately, data loads in background
const { data, status } = await useLazyFetch('/api/heavy-data')
</script>

<template>
  <div v-if="status === 'pending'">
    <Skeleton />
  </div>
  <div v-else>
    {{ data }}
  </div>
</template>

Read the full file on GitHub · 416 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 416 lines · 0 tokens per session scan A c9e294ab7bc6

Subscribe to this mod's changes

nuxt is a cursor rule published in the GitHub repository Renvia-code/best-cursor-rules (12 stars, last pushed 9mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 2,079 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.