Clean API Foundation

Every new backend service used to start with the same week of setup: auth, errors, validation, logging, caching, encryption. Done differently each time, it drifted.

• Domain, use cases, adapters and infrastructure in strict layers, with dependencies pointing inward.
• Auth built in: JWT with encrypted payloads, token caching in Redis, password reset flows.
• Typed HTTP errors, a generic paginated repository, a lightweight DI container, Winston logging.

• New services start from a consistent, secure baseline.
• Engineers spend their first day on the product, not the plumbing.