programming-principleslisted

# Programming Principles Checklist A comprehensive checklist of programming principles for writing clean, maintainable, and robust code. Apply this checklist when writing new code, reviewing existing code, or refactoring. --- ## Skills To Load (Required) - skill:examples ## Instructions When invoked: 1. Read the code or description provided by the user. 2. Go through each section of the checklist below. 3. For each item, mark: ✅ (pass) / ❌ (fail) / ⚠️ (partial) / N/A. 4. For every ❌ or ⚠️, provide a specific, actionable suggestion. 5. Summarize findings at the end with a priority fix list. --- ## Checklist ### 1. Foundational Principles | # | Principle | Check | |---|-----------|-------| | 1.1 | **DRY** – Don't Repeat Yourself: No duplicated logic or data | [ ] | | 1.2 | **KISS** – Keep It Simple, Stupid: No unnecessary complexity | [ ] | | 1.3 | **YAGNI** – You Ain't Gonna Need It: No speculative features | [ ] | | 1.4 | **SoC** – Separation of Concerns: Each module has one clear purpose | [ ] | | 1.5 | **CoC** – Convention over Configuration: Follows language/framework conventions | [ ] | --- ### 2. SOLID Principles | # | Principle | Check | |---|-----------|-------| | 2.1 | **S** – Single Responsibility: Each class/function does exactly one thing | [ ] | | 2.2 | **O** – Open/Closed: Open for extension, closed for modification | [ ] | | 2.3 | **L** – Liskov Substitution: Subtypes are substitutable for their base types | [ ] | | 2.4 | **I** – Interface Segregatio