---

name: style-guide description: Code style and formatting guidelines

Style Guide

General Principles

1. Readability over cleverness
2. Consistency within codebase
3. Use linter/formatter

Naming

• Variables: camelCase, descriptive
• Functions: camelCase, verb-based
• Classes: PascalCase
• Constants: SCREAMING_SNAKE_CASE
• Files: kebab-case

Functions

• Do one thing well
• Max ~50 lines
• Clear parameters
• Return early

Files

• Max ~300 lines
• One concept per file
• Clear organization

Comments

• Explain why, not what
• Keep current
• Use for complex logic

Commits

Copy{type}({scope}): {description}

Types: feat, fix, test, refactor, docs, chore