awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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.
git clone --depth 1 https://github.com/sanjeed5/awesome-cursor-rules-mdcWrote 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.
[](https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/next-js)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/next-js"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/next-js.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02952 | $0.02952 |
| Opus 5 | $0.01476 | $0.01476 |
| Sonnet 5 | $0.00590 | $0.00590 |
| Haiku 4.5 | $0.00295 | $0.00295 |
Grade A, and why
next-js 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
next-js Best Practices
This document outlines the definitive best practices for developing Next.js applications. Adhering to these guidelines ensures consistent, performant, and maintainable code, leveraging Next.js's strengths for modern web development.
1. Code Organization and Structure
Always use the app/ directory for new projects. Organize code by feature, not by type, to improve discoverability and cohesion.
✅ GOOD: Feature-Driven app/ Directory
Group all related files for a feature (components, pages, layouts, hooks, types) within a single directory.
// app/dashboard/page.tsx
export default function DashboardPage() { /* ... */ }
// app/dashboard/layout.tsx
export default function DashboardLayout({ children }) { /* ... */ }
// app/dashboard/components/DashboardOverview.tsx
export function DashboardOverview() { /* ... */ }
// app/dashboard/hooks/useDashboardData.ts
export function useDashboardData() { /* ... */ }
❌ BAD: Type-Driven app/ Directory
Avoid scattering files of the same feature across different top-level type directories.
// app/dashboard/page.tsx
// components/dashboard/DashboardOverview.tsx // Separated
// hooks/useDashboardData.ts // Separated
Core Directories
app/: All route-related files (page.tsx,layout.tsx,loading.tsx,error.tsx,route.ts).components/: Reusable UI components that are not directly tied to a specific route.lib/: Backend-agnostic utility functions, data access layers, and third-party integrations.hooks/: Custom React hooks for reusable logic.types/: Global TypeScript type definitions and interfaces.public/: Static assets (images, fonts) that are served directly.
2. Component Architecture: Server Components First
Prioritize Server Components for all UI rendering. Use Client Components only when interactivity (state, effects, event handlers) is strictly required.
✅ GOOD: Server Component by Default
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.
- 4d ago First seen · 449 lines · 2,952 tokens per session scan A 941112210183
next-js is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 2,952 tokens to every session, about $0.0148 per session on Opus 5. 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.
Other cursor rules, from other repositories
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
new-component
Workflow for creating new React components.
middleware-auth
Next.js middleware auth — prevents auth logic being placed in middleware instead of route handlers.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
common-fixes
Utility for VAN QA common validation fixes.