Software Architecture

This is a practical prompt for writing better code through clean architecture and domain-driven design principles. Use it when you want Claude to help with code structure, architecture decisions, or refactoring. It emphasizes library-first thinking (don't reinvent auth or retry logic), early returns over nested conditions, and domain-specific naming instead of generic utils folders. The take is opinionated but sensible: every line of custom code is a liability, so reach for established solutions first and only write custom code for actual business logic. Good for teams that want consistent architectural patterns without building everything from scratch.