coding-style

A set of coding conventions for C#, TypeScript, Angular, and Python, covering immutability, file structure, naming, and error handling.

In plain words
What is it for?
Use it when creating files, naming code, designing project layers, managing application state, choosing data types, and handling expected failures.
Why use it?
It makes code more predictable to read and change by setting shared rules for how projects are organized and written.

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/mckruz/claude-code-mastery/coding-style
Clone the repo
git clone --depth 1 https://github.com/MCKRUZ/claude-code-mastery
Per session 532 This file is loaded in full into every session.
When invoked 532 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.00532 $0.00532
Opus 5 $0.00266 $0.00266
Sonnet 5 $0.00106 $0.00106
Haiku 4.5 $0.00053 $0.00053

Measured 2d ago against content hash 08a23799c596, 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 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.

cursor-export/project-rules/coding-style.mdc · 41 lines

How it starts

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

Coding Style

Immutability (CRITICAL)

  • C#: IReadOnlyList/IReadOnlyDictionary<K,V> for public surfaces, readonly arrays for private backing fields, init-only properties for DTOs/config. Use records for simple value types, but NOT for polymorphic hierarchies (use classes with factory methods instead).
  • TypeScript: spread operators, never mutate objects/arrays. { ...obj, key } and [...arr, item].
  • NgRx reducers: always return new state objects.

File Organization

  • Clean Architecture with type-organized layers (Exceptions, Extensions, Interfaces, Models, Services — not feature folders within layers).
  • Many small files > few large files. Most files under 150 lines, 400 max.
  • High cohesion, low coupling. One class per file.

Naming

  • C#: PascalCase (classes/methods/props), _camelCase (private fields), camelCase (locals/params), I prefix for interfaces.
  • TypeScript: PascalCase (types/classes), camelCase (vars/funcs), kebab-case (files).
  • Python: snake_case (functions/variables), PascalCase (classes), UPPER_SNAKE_CASE (constants).

Error Handling

  • C#: Result for expected failures (validation, auth, business rules). Exceptions only for truly exceptional conditions. Factory methods: Result<T>.Success(value), Result<T>.Fail(message), Result.ValidationFailure(errors).
  • Angular: catchError in pipes, use logger service (no console.log), notify user.
  • Always: structured JSON logging, never swallow errors silently.

Validation

  • C#: FluentValidation on all DTOs, auto-discovered via assembly scanning, applied through MediatR pipeline behavior. Parallel validation with Task.WhenAll.
  • Angular: Reactive Forms with validators.
  • Validate at system boundaries only — trust internal code.

Dependency Injection

  • Each layer provides DependencyInjection.cs with Add*Dependencies() extension methods.
  • Use keyed DI (AddKeyedSingleton/Transient) for extensible registrations (tools, connectors).
  • MediatR pipeline behavior order matters — document registration order in DI.

Read the full file on GitHub · 41 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. 2d ago First seen · 41 lines · 532 tokens per session scan A 08a23799c596

Subscribe to this mod's changes

coding-style is a cursor rule published in the GitHub repository MCKRUZ/claude-code-mastery (11 stars, last pushed 4mo ago), licensed MIT. It adds 532 tokens to every session, about $0.0027 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.