coding-style

A set of rules for keeping source code consistent, including how data is changed, how functions are split, how files are organized, and how names are chosen.

In plain words
What is it for?
It guides work on application code by encouraging unchanged data, focused functions, smaller files, clear folders, and consistent naming.
Why use it?
It reduces confusion caused by different coding habits and makes code easier to read, change, and review.

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/jy315189/everything-cursor/coding-style
Clone the repo
git clone --depth 1 https://github.com/jy315189/everything-cursor

Made for: Cursor.

Per session 884 This file is loaded in full into every session.
When invoked 884 The same file — it is already loaded in full.
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.00884 $0.00884
Opus 5 $0.00442 $0.00442
Sonnet 5 $0.00177 $0.00177
Haiku 4.5 $0.00088 $0.00088

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

Security

Grade A, and why

coding-style 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.

.cursor/rules/coding-style.mdc · 154 lines

How it starts

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

Coding Style Guidelines

Core Principles

1. Immutability

NEVER mutate, ALWAYS create new:

// Arrays
const added = [...items, newItem]
const removed = items.filter(i => i.id !== id)
const updated = items.map(i => i.id === id ? { ...i, ...changes } : i)

// Objects
const updated = { ...user, name: newName }
const nested = { ...obj, nested: { ...obj.nested, value: newValue } }

2. Small Functions

Keep functions under 50 lines:

// BAD: Large function doing multiple things
function processOrder(order) {
  // 100+ lines of code...
}

// GOOD: Split into focused functions
function validateOrder(order: Order): ValidationResult { }
function calculateTotal(items: Item[]): number { }
function applyDiscounts(total: number, discounts: Discount[]): number { }
function createInvoice(order: Order, total: number): Invoice { }

3. Small Files

Keep files under 800 lines:

src/
├── features/
│   └── checkout/
│       ├── components/
│       │   ├── CartItem.tsx       # ~100 lines
│       │   ├── CartSummary.tsx    # ~80 lines
│       │   └── CheckoutForm.tsx   # ~150 lines
│       ├── hooks/
│       │   └── useCheckout.ts     # ~50 lines
│       └── services/
│           └── checkout.ts        # ~100 lines

4. Explicit Types

No implicit any:

// BAD
function process(data) {
  return data.map(item => item.value)
}

// GOOD
function process(data: DataItem[]): string[] {
  return data.map(item => item.value)
}

5. Error Handling

Always handle errors:

async function fetchUser(id: string): Promise<Result<User>> {
  try {
    const user = await db.users.findUnique({ where: { id } })
    if (!user) {
      return { success: false, error: 'User not found' }
    }
    return { success: true, data: user }
  } catch (error) {
    console.error('Failed to fetch user:', error)
    return { success: false, error: 'Failed to fetch user' }
  }
}

Code Review Checklist

Structure

  • Functions < 50 lines
  • Files < 800 lines
  • No deep nesting (> 4 levels)
  • Single responsibility

Read the full file on GitHub · 154 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 · 154 lines · 884 tokens per session scan A 53637d52a29d

Subscribe to this mod's changes

coding-style is a cursor rule published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 6mo ago), licensed MIT. It adds 884 tokens to every session, about $0.0044 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-08-31.