What problem does it solve?
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments. They reduce cognitive load and maintenance costs by enforcing simple, predictable rules and discouraging unnecessary boilerplate.
Core Features & Use Cases
- SRP (Single Responsibility) and DRY (Don't Repeat Yourself) guide function/class design to stay focused and reusable.
- KISS (Keep It Simple) and YAGNI (You Aren't Gonna Need It) principles to avoid over-engineering and feature creep.
- Naming & style rules to improve readability, including clear variable/function names and consistent boolean predicates.
- Code structure expectations, guard clauses, and avoidance of deep nesting to improve maintainability.
- Self-checks and guardrails for code quality, including pre-edit thinking and mandatory checks before completing tasks.
Quick Start
Start a new module by writing a small, focused function that adheres to SRP, then refactor to remove duplication and unnecessary comments.