Webman framework best practices following DDD architecture, dependency rules, and PER Coding Style.

Architecture & Dependencies

Controller directly depends on Model, skipping Service layer → See controller-skip-service
Domain layer depends on framework classes (Request, DB, etc.) → See domain-framework-dependency
Service layer has circular dependencies with another Service → See service-circular-dependency
Infrastructure layer not implementing Contract interface → See infrastructure-without-contract
Using Model directly in Service instead of Repository → See service-direct-model-access

Naming Conventions

Using camelCase or PascalCase for directories → See directory-lowercase
Interface without Interface suffix → See interface-naming
Service not following VerbNounService pattern → See service-naming-pattern
Repository implementation without descriptive prefix → See repository-implementation-naming
Namespace not matching directory structure → See namespace-directory-mismatch