| Architecture Decision Records (ADRs): Format and Purpose | concept | 3 | Open |
| Automated Checks as Part of Design Hygiene | concept | 5 | Open |
| Book Exercise Lanes | exercise | 12 | Open |
| Choosing Patterns as a Response to Design Pressure | concept | 3 | Open |
| Code Review Rubrics: Correctness, Clarity, Design, Tests | concept | 3 | Open |
| Combining Patterns: Decorator + Strategy + Factory in One Feature | concept | 2 | Open |
| Design Documents for Small-to-Medium Features | concept | 4 | Open |
| Designing for Testability without Damaging the Domain | concept | 3 | Open |
| Learning Resources | resource | 13 | Open |
| Long-Term Code Stewardship: Boy-Scout Rule, Broken Windows, Narrative Git History | concept | 4 | Open |
| Over-Engineering vs Under-Engineering: Reading the Context | concept | 3 | Open |
| Receiving Feedback: Disagreement, Defense, and Growth | concept | 2 | Open |
| Reference and Selective Reading | reference | 17 | Open |
| Reversibility: One-Way vs Two-Way Doors | concept | 3 | Open |
| Reviewable Commits and Pull-Request Shape | concept | 3 | Open |
| Sequence Diagrams, C4 Model, and When a Picture Pays for Itself | concept | 1 | Open |
| Simple Design: The Four Rules | concept | 4 | Open |
| Writing Review Comments: Specific, Constructive, Evidence-Based | concept | 4 | Open |