clean-architecture

Apply Robert C. Martin's Clean Architecture when writing, placing, reviewing, or refactoring application code — the dependency rule, layer responsibilities, use-case boundaries, ports and adapters, and keeping frameworks, databases, and UI as replaceable details. Use when adding a feature to a layered codebase, deciding which layer new code belongs in, designing module or package structure, introducing an interface for an external dependency, reviewing a diff for boundary violations, or breaking up a god service. Do not use for throwaway scripts, one-file prototypes, config-only edits, or codebases that have deliberately chosen a different architectural style.