001-code-style

A set of rules for readable source code, covering names, formatting, function signatures, component design, and common mistakes to avoid.

In plain words
What is it for?
Use it to choose names and formatting, require explicit return types, handle promise errors, organize UI code, and replace unsafe or unclear patterns such as unrestricted any types.
Why use it?
It keeps code consistent and easier to read, while reducing unclear names, hidden errors, and business logic placed in the wrong layer.

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/obviousworks/vibe-coding-ai-rules/001-code-style
Clone the repo
git clone --depth 1 https://github.com/obviousworks/vibe-coding-ai-rules

Made for: Cursor.

Per session 297 This file is loaded in full into every session.
When invoked 297 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.00297 $0.00297
Opus 5 $0.00148 $0.00148
Sonnet 5 $0.00059 $0.00059
Haiku 4.5 $0.00030 $0.00030

Measured 2d ago against content hash 863b41da9396, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

001-code-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 2d 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.

ide-specific/cursor/.cursor/rules/001-code-style.mdc · 38 lines

What it actually says

Code Style & Conventions

Naming Conventions

  • Files: {{FILE_NAMING}} (e.g., kebab-case.tsx, snake_case.py)
  • Components: PascalCase
  • Functions: camelCase with verb prefixes (getUserData, calculateTotal)
  • Variables: camelCase with auxiliary verbs for booleans (isLoading, hasError)
  • Constants: UPPER_SNAKE_CASE
  • Types/Interfaces: PascalCase

Formatting

  • Indentation: {{INDENTATION}} (e.g., 2 spaces)
  • Line Length: {{LINE_LENGTH}} max (e.g., 100 chars)
  • Quotes: {{QUOTE_STYLE}} (e.g., single quotes)
  • Semicolons: {{SEMICOLONS}} (e.g., required)
  • Trailing Commas: always in multi-line structures

Readability

Code must be immediately understandable. Use descriptive naming. Maintain clear structure. Readable code over clever code.

Do's

  • Use explicit return types for functions
  • Prefer composition over inheritance
  • Use const assertions for literal types
  • Implement proper error boundaries

Don'ts

  • No any types — use unknown with type guards
  • No unhandled promise rejections
  • No inline styles (use CSS framework)
  • No business logic in UI components
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. 2d ago First seen · 38 lines · 297 tokens per session scan A 863b41da9396

Subscribe to this mod's changes

001-code-style is a cursor rule published in the GitHub repository obviousworks/vibe-coding-ai-rules (88 stars, last pushed 2mo ago), licensed MIT. It adds 297 tokens to every session, about $0.0015 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-30.