nextjs

A set of project rules for building Next.js applications, a React framework for web pages and server-side features. It covers file structure, component choice, naming, data loading, and form handling.

In plain words
What is it for?
Use it when creating or changing JavaScript or TypeScript files in a Next.js application, especially routes, components, forms, and data-fetching code.
Why use it?
It gives coding agents consistent conventions for Next.js projects and helps avoid unnecessary client-side code and inconsistent organization.

Cursor rule for Cursor

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/wangtingyeye/llm-agent-study/nextjs
Clone the repo
git clone --depth 1 https://github.com/WangTingYeYe/llm-agent-study

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 298 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.00298
Opus 5 $0.00000 $0.00149
Sonnet 5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

Measured 2d ago against content hash 0775479225b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nextjs 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 2d 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.

.cursor/rules/frameworks/nextjs.mdc · 26 lines

What it actually says


description: 该规则解释了 Next.js 全栈开发的约定和最佳实践。 globs: /*.js,/.jsx,**/.ts,**/*.tsx alwaysApply: false

Next.js 规则

  • 使用 App Router 结构,在路由目录中使用 page.tsx 文件。
  • 客户端组件必须在文件顶部明确标记 'use client'
  • 目录名使用 kebab-case(例如 components/auth-form),组件文件使用 PascalCase。
  • 优先使用命名导出而非默认导出,即使用 export function Button() { /* ... */ } 而不是 export default function Button() { /* ... */ }
  • 尽量减少 'use client' 指令:
    • 保持大多数组件为 React Server Components (RSC)
    • 仅在需要交互性时使用客户端组件,并用带有 fallback UI 的 Suspense 包装
    • 为交互元素创建小型客户端组件包装器
  • 尽可能避免不必要的 useStateuseEffect
    • 使用服务器组件进行数据获取
    • 使用 React Server Actions 处理表单
    • 使用 URL 搜索参数实现可共享状态
  • 使用 nuqs 管理 URL 搜索参数状态
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. 2d ago First seen · 26 lines · 0 tokens per session scan A 0775479225b8

Subscribe to this mod's changes

nextjs is a cursor rule published in the GitHub repository WangTingYeYe/llm-agent-study (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 298 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-31.