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/nextjs-supabase-shadcn-pwa-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/nextjs-supabase-shadcn-pwa-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/nextjs-supabase-shadcn-pwa-cursorrules-prompt-file/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/nextjs-supabase-shadcn-pwa-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/nextjs-supabase-shadcn-pwa-cursorrules-prompt-file.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.01424 | $0.01424 |
| Opus 5 | $0.00712 | $0.00712 |
| Sonnet 5 | $0.00285 | $0.00285 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
nextjs-supabase-shadcn-pwa-cursorrules-prompt-file 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 6d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Key Principles
-
Code Quality & Style
- Write concise, maintainable, and strongly typed code with accurate TypeScript implementations.
- Embrace functional, declarative programming. Avoid OOP and classes.
- Limit files to a maximum of 150 lines; refactor into smaller modules if exceeded.
- Prefer iteration and modularization over duplication.
- Use descriptive, semantic variable names with auxiliary verbs (e.g.,
isLoading,hasError). - Use lowercase with dashes for directories and files (e.g.,
components/auth-wizard). - Favor named exports for components.
- Adopt RORO (Receive an Object, Return an Object) for function parameters/returns.
- Always attain to use DRY (Don't Repeat Yourself) principles.
- Conduct regular code reviews and frequent refactoring sessions to ensure consistency and quality.
- Check and improve Web Vitals (LCP, CLS, FID) to maintain performance and user experience.
-
Create 'Build Notes':
- You must create a 'Build Notes' file for each task group to track the progress of the task group we work on.
- Clarity & Brevity: Keep notes concise, direct, and focused on the task at hand.
- Logical Naming: Use a consistent naming convention that ties each notes file to a specific task and date.
- Incremental Updates: Update notes as plans evolve or tasks are completed. Append rather than overwrite.
- Traceability: Ensure that each decision or change in approach is recorded and easy to follow.
-
Review 'Project Contexts':
- You must review the
projectContext.mdas we need to ensure that the project context is up to date and accurate. - Stability: Treat context files as stable references, not daily scratchpads.
- Selective Updates: Update context files only when there are significant, approved changes to requirements or project scope.
- Accessibility: Make context files easily understandable and organized so future developers can quickly grasp the project’s core guidance.
- You must review the
-
Stack and Framework Conventions
- Target Next.js 15+ and leverage the App Router, React Server Components (RSC), and SSR capabilities.
- Use Zustand for state management in client components when necessary.
- Maintain proper Shadcn UI management using
npx shadcn@latest addfor new components. - Follow a mobile-first approach and responsive design patterns.
- Emphasize server-side logic, minimizing the usage of
use clientand other client-only APIs. - Structure project as Progressive Web App (PWA) with offline capabilities, app-like experience, and installability across devices.
-
Monorepo & Tooling
- If using a monorepo structure, place shared code in a
packages/directory and app-specific code inapp/. - Use
Taskfile.ymlcommands for development, testing, and deployment tasks. - Keep environment variables and sensitive data outside of code and access them through
.envfiles or similar configuration.
- If using a monorepo structure, place shared code in a
Below is a structured guideline to provide to the AI development agent, incorporating key principles and detailed rules for maintaining the /ProjectDocs/Build_Notes/ and /ProjectDocs/contexts/ directories.
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.
- 6d ago First seen · 121 lines · 1,424 tokens per session scan A f27691328540
nextjs-supabase-shadcn-pwa-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,748 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 1,424 tokens to every session, about $0.0071 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
vue3-typescript-auto
Vue 3 with TypeScript Standards.
angular
Angular: signals, standalone components, RxJS patterns.
typescript
TypeScript coding standards and best practices for modern web development.
typescript-code-generation-rules
description: Rules for generating TypeScript code in Next.js 14 components, including component definition syntax, props definitions, and named/default exports. globs: /.tsx.
react-and-typescript-general-rules
description: General rules for React and TypeScript projects, focusing on code clarity and best practices. globs: /.{ts,tsx,js,jsx}.
key-conventions
Key coding conventions for Astro projects including style guide and typescript.