System Design

This is an opinionated architecture guide that pushes you toward Clean Architecture and DDD principles with some practical guardrails. The interesting bit is how strongly it emphasizes library-first development, telling you to search npm and existing SaaS before writing custom code, with specific examples like using cockatiel for retries instead of rolling your own. It enforces early returns, bans generic file names like utils.js and helpers.js in favor of domain-specific naming, and keeps functions under 50 lines and files under 200. The anti-patterns section is refreshingly direct about NIH syndrome. If you want Claude to be more pragmatic about leveraging existing solutions and less likely to reinvent wheels, this adds useful constraints to system design conversations.