clean-code

A set of guidelines for writing code that is easy to read, test, and maintain. It covers naming, simple functions, consistent patterns, and clear structure.

In plain words
What is it for?
Use it when naming variables and functions, splitting up logic, reviewing code, designing testable functions, and keeping a project consistent.
Why use it?
It reduces the time developers spend guessing what code means or untangling complicated changes.

Cursor rule

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/renvia-code/best-cursor-rules/clean-code
Clone the repo
git clone --depth 1 https://github.com/Renvia-code/best-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,926 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.01926
Opus 5 $0.00000 $0.00963
Sonnet 5 $0.00000 $0.00385
Haiku 4.5 $0.00000 $0.00193

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

Security

Grade A, and why

clean-code 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.

rules/best-practices/clean-code.mdc · 349 lines

How it starts

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

Clean Code Best Practices

Overview

Principle Description
Readability Code is read more than written
Simplicity Simple is better than complex
Consistency Follow established patterns
Testability Write code that's easy to test

Naming Conventions

Use Descriptive Names

// ❌ Bad - Unclear names
const d = new Date()
const u = getUser()
function calc(a, b) { return a + b }

// ✅ Good - Clear, descriptive names
const currentDate = new Date()
const authenticatedUser = getUser()
function calculateTotal(price, quantity) { return price * quantity }

Use Consistent Naming Patterns

// Boolean variables: is, has, should, can
const isActive = true
const hasPermission = user.role === 'admin'
const shouldRefresh = lastUpdate < Date.now() - 60000
const canEdit = hasPermission && isActive

// Functions: verb + noun
function getUser(id: string) {}
function createOrder(data: OrderData) {}
function validateEmail(email: string) {}
function calculateDiscount(price: number) {}

// Event handlers: handle + event
function handleClick() {}
function handleSubmit() {}
function handleUserCreated() {}

Functions

Keep Functions Small and Focused

// ❌ Bad - Does too many things
function processOrder(order) {
  // Validate order
  if (!order.items) throw new Error('No items')
  if (!order.userId) throw new Error('No user')
  
  // Calculate total
  let total = 0
  for (const item of order.items) {
    total += item.price * item.quantity
  }
  
  // Apply discount
  if (order.coupon) {
    total *= 0.9
  }
  
  // Save to database
  db.orders.create({ ...order, total })
  
  // Send email
  sendEmail(order.userId, 'Order confirmed')
}

// ✅ Good - Single responsibility
function validateOrder(order: Order): void {
  if (!order.items?.length) throw new Error('Order must have items')
  if (!order.userId) throw new Error('Order must have userId')
}

function calculateOrderTotal(items: OrderItem[], coupon?: Coupon): number {
  const subtotal = items.reduce((sum, item) => sum + item.price * item.quantity, 0)
  return coupon ? applyDiscount(subtotal, coupon) : subtotal
}

function processOrder(order: Order): void {
  validateOrder(order)
  const total = calculateOrderTotal(order.items, order.coupon)
  saveOrder({ ...order, total })
  notifyUser(order.userId, 'Order confirmed')
}

Read the full file on GitHub · 349 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 · 349 lines · 0 tokens per session scan A d74510d4b1ea

Subscribe to this mod's changes

clean-code is a cursor rule published in the GitHub repository Renvia-code/best-cursor-rules (12 stars, last pushed 9mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 1,926 tokens. 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.