How I work

POC and project skeleton

After the tree and before the first feature, I build the skeleton: folders with one responsibility each, a linter and formatting enforced by CI, mandatory coverage, a one-command local stack and the design patterns everyone will follow. That is what stops a project from becoming everyone's own way.

Decisions and why

.editorconfig and linter in the first commit
180 columns, 4 spaces, one parameter per line: the style discussion ends before it starts and CI blocks what drifts.
Folders by role, not by technology
controller/, use_case/, rule/, client/, repository/: newcomers find anything without asking.
Single-execute use cases, Strategy for locks, Repository and DI
Each action isolated, each lock pluggable and each dependency coming in through the constructor.
Coverage gate from day one
Reaching 100% later is impossible; from the start it is just habit.
A custom lint rule when a mistake repeats
Fields without a mask became no-restricted-imports: the mistake does not come back.
requestresponse
Pick a scenario above to watch the message travel through the architecture.