nextjs-patterns

A collection of patterns and code templates for pages and interactive components in the Next.js App Router, including server-rendered pages and client-side actions.

In plain words
What is it for?
Use it when building or reviewing Next.js 14 App Router pages, loading states, interactive components, or refresh behavior.
Why use it?
It gives developers known structures for loading data, handling missing pages, adding metadata, and separating server work from browser interactions.

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/farzannajipour/cursor-react-rules/nextjs-patterns
Clone the repo
git clone --depth 1 https://github.com/Farzannajipour/cursor-react-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 905 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.00905
Opus 5 $0.00000 $0.00452
Sonnet 5 $0.00000 $0.00181
Haiku 4.5 $0.00000 $0.00090

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

Security

Grade A, and why

nextjs-patterns 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.

.cursor/rules/nextjs-patterns.mdc · 173 lines

How it starts

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

Next.js App Router Patterns

Pattern: Server Component Page

import { Suspense } from 'react';
import { notFound } from 'next/navigation';

export async function generateMetadata({ params }: { params: { id: string } }) {
  const data = await fetchData(params.id);
  return {
    title: data.title,
    description: data.description,
  };
}

export default async function Page({ params }: { params: { id: string } }) {
  const data = await fetchData(params.id);

  if (!data) notFound();

  return (
    <div>
      <h1>{data.title}</h1>
      <Suspense fallback={<LoadingSkeleton />}>
        <AsyncContent id={params.id} />
      </Suspense>
    </div>
  );
}

export const revalidate = 3600; // ISR

Pattern: Client Component for Interactivity

'use client';

import { useState } from 'react';
import { useRouter } from 'next/navigation';

export function InteractiveComponent({ initialData }: { initialData: Data }) {
  const router = useRouter();
  const [data, setData] = useState(initialData);

  const handleAction = async () => {
    // Client-side logic
    router.refresh(); // Refresh server data
  };

  return <div onClick={handleAction}>{data.title}</div>;
}

Pattern: Server Action

'use server';

import { revalidatePath } from 'next/cache';
import { z } from 'zod';
import { db } from '@/lib/db';

const schema = z.object({
  name: z.string().min(1),
});

export async function createItem(formData: FormData) {
  try {
    const validated = schema.parse({
      name: formData.get('name'),
    });

    const item = await db.item.create({
      data: validated,
    });

    revalidatePath('/items');
    return { success: true, data: item };
  } catch (error) {
    return { success: false, error: 'Failed to create item' };
  }
}

Pattern: API Route Handler

import { NextRequest, NextResponse } from 'next/server';
import { z } from 'zod';

const schema = z.object({
  name: z.string(),
});

export async function GET(request: NextRequest) {
  const searchParams = request.nextUrl.searchParams;
  const query = searchParams.get('q');
  
  const items = await db.item.findMany({
    where: { name: { contains: query } },
  });

  return NextResponse.json(items);
}

export async function POST(request: NextRequest) {
  try {
    const body = await request.json();
    const validated = schema.parse(body);

    const item = await db.item.create({ data: validated });

    return NextResponse.json(item, { status: 201 });
  } catch (error) {
    return NextResponse.json(
      { error: 'Invalid request' },
      { status: 400 }
    );
  }
}

Read the full file on GitHub · 173 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 · 173 lines · 0 tokens per session scan A 51d023ff5718

Subscribe to this mod's changes

nextjs-patterns is a cursor rule published in the GitHub repository Farzannajipour/cursor-react-rules (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 905 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.