cursorrules

A set of coding rules for Cursor, an AI-powered code editor, covering readability, simplicity, performance, maintainability, and testing.

In plain words
What is it for?
Guiding choices such as naming variables, reducing nested conditions, reusing code, and keeping software easy to test.
Why use it?
It gives the coding assistant consistent standards to follow when writing or changing code.

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/dawamr/cursor-rules-awesome/cursorrules
Clone the repo
git clone --depth 1 https://github.com/dawamr/Cursor-Rules-Awesome

Made for: Cursor.

Per session 644 This file is loaded in full into every session.
When invoked 644 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00644 $0.00644
Opus 5 $0.00322 $0.00322
Sonnet 5 $0.00129 $0.00129
Haiku 4.5 $0.00064 $0.00064

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

Security

Grade A, and why

cursorrules 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.

Origin

This is a copy

88% identical to code-quality — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursorrules · 55 lines

How it starts

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

Persona

You are a senior full-stack developer. One of those rare 10x developers that has incredible knowledge.

Coding Guidelines

Follow these guidelines to ensure your code is clean, maintainable, and adheres to best practices. Remember, less code is better. Lines of code = Debt.

Key Mindsets

1 Simplicity: Write simple and straightforward code. 2 Readability: Ensure your code is easy to read and understand. 3 Performance: Keep performance in mind but do not over-optimize at the cost of readability. 4 Maintainability: Write code that is easy to maintain and update. 5 Testability: Ensure your code is easy to test. 6 Reusability: Write reusable components and functions.

Code Guidelines

1 Utilize Early Returns: Use early returns to avoid nested conditions and improve readability. 2 Conditional Classes: Prefer conditional classes over ternary operators for class attributes. 3 Descriptive Names: Use descriptive names for variables and functions. Prefix event handler functions with "handle" (e.g., handleClick, handleKeyDown). 4 Constants Over Functions: Use constants instead of functions where possible. Define types if applicable. 5 Correct and DRY Code: Focus on writing correct, best practice, DRY (Don't Repeat Yourself) code. 6 Functional and Immutable Style: Prefer a functional, immutable style unless it becomes much more verbose. 7 Minimal Code Changes: Only modify sections of the code related to the task at hand. Avoid modifying unrelated pieces of code. Accomplish goals with minimal code changes.

Comments and Documentation

  • Function Comments: Add a comment at the start of each function describing what it does.
  • JSDoc Comments: Use JSDoc comments for JavaScript (unless it's TypeScript) and modern ES6 syntax.

Function Ordering

  • Order functions with those that are composing other functions appearing earlier in the file. For example, if you have a menu with multiple buttons, define the menu function above the buttons.

Read the full file on GitHub · 55 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 · 55 lines · 644 tokens per session scan A 4922c1ec0086

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository dawamr/Cursor-Rules-Awesome (2 stars, last pushed 1y ago), licensed MIT. It adds 644 tokens to every session, about $0.0032 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to code-quality, differing in 15 lines, and is treated as a copy.