Enforce clean architecture layer separation and inward dependency flow in Go projects.
npx skills add https://github.com/baphled/dotopencode --skill architecture-baphled
Please help me install this Agent Skill. Skill: architecture Source: https://github.com/baphled/dotopencode/tree/main/skills/architecture Command: npx skills add https://github.com/baphled/dotopencode --skill architecture-baphled
This Skill enforces clean architecture principles, ensuring layer separation, correct dependency direction, and boundary rules to maintain a clean and scalable codebase.
Use the architecture skill to review the current Go project structure for layer boundary violations.
High-intent search queries and answers about installing and using this skill.
To enforce clean architecture in a Go project, ensure domain, service, repository, and handler layers are distinct. Verify that dependencies flow inward toward the domain core, keeping infrastructure concerns isolated from business logic.
The best way to structure feature-based packages in clean architecture is to organize code by domain features, placing logic in appropriate layers like domain, service, and handler. This maintains layer isolation and inward dependency flow for scalable codebases.
To prevent outward dependencies from polluting domain logic, apply interface-based repository patterns and service orchestration. This keeps the core domain free from external framework or infrastructure concerns by enforcing strict boundary rules.
Yes, you can use dependency injection in Golang service architecture to manage layers. It facilitates service orchestration and ensures dependencies flow correctly inward, keeping the domain layer isolated from infrastructure and framework implementations.
You need interface-based repository patterns for code quality when separating domain logic from data access. This approach enforces clean architecture by defining contracts at the domain layer, preventing direct infrastructure dependencies.
Clean architecture reviews fail on layer boundary violations when dependencies flow outward instead of inward. This happens when domain or service layers directly reference infrastructure or handler components, breaking the required layer isolation.
saddam-eng-techGenerate Go gRPC microservice scaffolds with Clean Architecture layers.
CsHengValidate Go code through compilation, linting, testing, and dependency checks.
LuigiAPCPereiraAnalyze Golang projects for dependency injection and recommend improvements.
ccfDesign backend systems with Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.
