coding-standards

Topics in the source

• Coding Standards & Best Practices
• When to Activate
• Code Quality Principles
• 1. Readability First
• 2. KISS (Keep It Simple, Stupid)
• 3. DRY (Don't Repeat Yourself)
• 4. YAGNI (You Aren't Gonna Need It)
• TypeScript/JavaScript Standards

Universal coding standards applicable across all projects. Starting a new project or module Reviewing code for quality and maintainability Refactoring existing code to follow conventions Enforcing naming, formatting, or structural consistency Setting up linting, formatting, or type-checking rules Onboarding new contributors to coding conventions Code is read more than written Clear variable and function names Self-documenting code preferred over comments Consistent formatting Simplest solution that works Avoid over-engineering No premature optimization Easy to understand > clever code Extract common logic into functions Create reusable components Share utilities across modules Avoid copy-paste programming Don't build features before they're needed Avoid speculative generality Add complexity only when required Start simple, refactor when needed Watch for these anti-patterns: Remember: Code quality is not negotiable. Clear, maintainable code enables rapid development and confident refactoring.