next-js-conventions

next-js-conventions is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 0 tokens per session (150 once invoked), scanned A, original, MIT.

A set of Next.js conventions for state changes, web performance measurements, server rendering, data loading, and browser-side code.

In plain words
What is it for?
It helps structure Next.js App Router applications with server components, server rendering, controlled use of client components, and attention to Web Vitals such as loading speed and layout stability.
Why use it?
It helps avoid unnecessary client-side code while keeping important page performance measures in view.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit It helps structure Next.js App Router applications with server components, server rendering, controlled use of client components, and attention to Web Vitals such as loading speed and layout stability.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/holtwood/awesome-cursorrules-zh/next-js-conventions
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.

Clone the repo
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zh

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for next-js-conventions

README.md
[![agentmods](https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/next-js-conventions/github.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/next-js-conventions)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/next-js-conventions"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/next-js-conventions/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for next-js-conventions

Your own site · 80×15
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/next-js-conventions"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/next-js-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 150 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00150
Opus 5 $0.00000 $0.00075
Sonnet 5 $0.00000 $0.00030
Haiku 4.5 $0.00000 $0.00015

Measured 6d ago against content hash 38e3fed71028, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

next-js-conventions 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 6d ago.

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.

docs/rules/frontend/react/nextjs-react-ts/next-js-conventions.mdc · 12 lines

What it actually says

  • 依赖 Next.js App Router 进行状态变化。
  • 优先考虑 Web Vitals(LCP、CLS、FID)。
  • 最小化 'use client' 使用:
    • 优先使用服务器组件和 Next.js SSR 功能。
    • 仅在小组件中用于 Web API 访问时使用 'use client'。
    • 避免将 'use client' 用于数据获取或状态管理。
    • 参考 Next.js 文档中关于数据获取、渲染和路由的最佳实践。
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. 6d ago First seen · 12 lines · 150 tokens per session scan A 38e3fed71028

Subscribe to this mod's changes

next-js-conventions is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (233 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 150 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-09-03.