Architecture Patterns

This is basically a linter-as-documentation approach for backend architecture. It enforces clean architecture principles, layer separation (routers, services, repositories), project structure conventions, and test standards through reference files that Claude reads on demand. The standout feature is right-sizing: it adjusts enforcement strictness based on project tier (interview/MVP/production/enterprise), so you're not forced into repository patterns for a weekend hackathon but get blocking violations for production systems. Covers 13 rules across 5 categories, all tuned for FastAPI and React/Next.js. Useful when you want architectural guardrails that understand context instead of dogmatic one-size-fits-all enforcement.