nextjs

A set of Next.js development rules for XM Cloud starter projects. Next.js is a framework for building web applications, while XM Cloud is Sitecore’s cloud platform for managing website content.

In plain words
What is it for?
Use it when configuring or developing multilingual XM Cloud sites with Next.js, including routes, media domains, robots files, sitemaps, and environment settings.
Why use it?
It provides consistent guidance for language settings, images, API rewrites, environment variables, routing, and build configuration.

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/sitecore/xmcloud-starter-js/nextjs
Clone the repo
git clone --depth 1 https://github.com/Sitecore/xmcloud-starter-js

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,315 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.01315
Opus 5 $0.00000 $0.00658
Sonnet 5 $0.00000 $0.00263
Haiku 4.5 $0.00000 $0.00131

Measured 2d ago against content hash 37179514b13c, 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/nextjs.mdc · 210 lines

How it starts

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

Next.js Development Patterns

Configuration

Next.js Config:

  • Configure i18n for multi-language XM Cloud sites
  • Set up proper image domains for XM Cloud media
  • Implement rewrites for XM Cloud API routes
  • Configure webpack for SCSS and other assets
  • Set up proper build optimization
// next.config.js pattern
const nextConfig = {
  i18n: {
    locales: ['en', 'en-CA'],
    defaultLocale: process.env.DEFAULT_LANGUAGE || 'en',
  },
  images: {
    remotePatterns: [
      {
        protocol: 'https',
        hostname: 'edge*.**',
      },
      {
        protocol: 'https',
        hostname: 'xmc-*.**',
      },
    ],
  },
  async rewrites() {
    return [
      {
        source: '/robots.txt',
        destination: '/api/robots',
      },
      {
        source: '/sitemap.xml',
        destination: '/api/sitemap',
      },
    ];
  },
};

Environment Variables:

  • Use NEXT_PUBLIC_ prefix for client-side variables
  • Validate required environment variables at build time
  • Use different .env files for different environments
  • Never commit sensitive environment variables

App Router Pages and Routing

Catch-All Routes:

  • Use src/app/[site]/[locale]/[[...path]]/page.tsx for XM Cloud page routing
  • Fetch layout data in the Server Component with sitecore-client
  • Call notFound() when the route does not exist
  • Use draftMode() and editing search params for preview and Pages Editor
// page.tsx pattern (App Router)
export default async function Page({ params, searchParams }: PageProps) {
  const { site, locale, path } = await params;
  const draft = await draftMode();

  let page;
  if (draft.isEnabled) {
    const editingParams = await searchParams;
    page = await client.getPreview(editingParams);
  } else {
    page = await client.getPage(path ?? [], { site, locale });
  }

  if (!page) {
    notFound();
  }

  return (/* Layout + Providers */);
}

Pages Router:

  • Only examples/basic-nextjs-pages-router uses src/pages/[[...path]].tsx with getStaticProps / getServerSideProps
  • Do not add Pages Router patterns to App Router starters

Read the full file on GitHub · 210 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. 2d ago First seen · 210 lines · 0 tokens per session scan A 37179514b13c

Subscribe to this mod's changes

nextjs is a cursor rule published in the GitHub repository Sitecore/xmcloud-starter-js (29 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,315 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.