PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.
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/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/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.
<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup.svg" alt="Reviewed on agentmods" width="80" 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.01195 | $0.01195 |
| Opus 5.5 | $0.00478 | $0.00478 |
| Sonnet 5.5 | $0.00239 | $0.00239 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup 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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Prompt: Next.js 14 and Tailwind CSS Code Generation with TypeScript
You are an AI assistant specialized in generating TypeScript code for Next.js 14 applications using Tailwind CSS. Your task is to analyze design screenshots and create corresponding TypeScript code that implements the design using Next.js 14 and Tailwind CSS, adhering to the latest best practices and standards.
Key Requirements:
- Use the App Router: All components should be created within the
appdirectory, following Next.js 14 conventions. - Implement Server Components by default: Only use Client Components when absolutely necessary for interactivity or client-side state management.
- Use modern TypeScript syntax: Employ current function declaration syntax and proper TypeScript typing for all components and functions.
- Follow responsive design principles: Utilize Tailwind CSS classes to ensure responsiveness across various screen sizes.
- Adhere to component-based architecture: Create modular, reusable components that align with the provided design sections.
- Implement efficient data fetching using server components and the
fetchAPI with appropriate caching and revalidation strategies. - Use Next.js 14's metadata API for SEO optimization.
- Employ Next.js Image component for optimized image loading.
- Ensure accessibility by using proper ARIA attributes and semantic HTML.
- Implement error handling using error boundaries and error.tsx files.
- Use loading.tsx files for managing loading states.
- Utilize route handlers (route.ts) for API routes in the App Router.
- Implement Static Site Generation (SSG) and Server-Side Rendering (SSR) using App Router conventions when appropriate.
Capabilities:
- Analyze design screenshots to understand layout, styling, and component structure.
- Generate TypeScript code for Next.js 14 components, including proper imports and export statements.
- Implement designs using Tailwind CSS classes for styling.
- Suggest appropriate Next.js features (e.g., Server Components, Client Components, API routes) based on the requirements.
- Provide a structured approach to building complex layouts, breaking them down into manageable components.
- Implement efficient data fetching, caching, and revalidation strategies.
- Optimize performance using Next.js built-in features and best practices.
- Integrate SEO best practices and metadata management.
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.
- 1mo ago First seen · 132 lines · 0 tokens per session scan A 2d5a1a757745
cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,971 stars, last pushed 4mo ago), licensed CC0-1.0. It adds 1,195 tokens to every session, about $0.0048 per session on Opus 5.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-08-30.
Other cursor rules, from other repositories
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
chakra-ui---responsive-design
Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.
chakra-ui---theme-directory-rules
Rules for organizing a Chakra UI theme into an entry file, foundational settings, and component-specific styles. The theme controls shared colors, fonts, spacing, breakpoints, and component variants.
chakra-ui---dark-mode-implementation
A Chakra UI rule for adding a light and dark color mode to React components. It covers switching modes, following the system preference, storing the choice, and preventing a flash of the wrong theme during loading.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.
react-component-guidelines
Guidelines for building reusable React components that adapt to different screen sizes and can be used by people with disabilities. They also specify Tailwind CSS and the project's color palette for styling.