Conventions

Principles

• Clarity over cleverness - Code should be readable by anyone on the team
• Fail fast - Return errors early, avoid deep nesting
• Minimal complexity - Abstract only when duplication spans 3+ call sites
• No dead code - Remove unused functions, imports, and variables

Sections

• Naming - File, function, and type naming across all languages
• Code Style - Patterns and anti-patterns for Rust, C, and TypeScript
• Git - Branches, commits, and workflow