golang-mvc

What problem does it solve?

Go projects often suffer from messy, tightly coupled code where MVC layer boundaries are violated—such as handlers directly accessing databases or business logic being placed in the wrong layer—making code hard to test, refactor, and maintain.

Core Features & Use Cases

• Strict Layer Boundary Enforcement: Clear import rules for each MVC layer (handler, service, repository, model, validation) to prevent cross-layer dependencies.
• End-to-End Implementation Guidance: Step-by-step checklist for building new features following MVC conventions, from model definition to final wiring.
• Refactoring Support: Rules and patterns to fix existing code that violates layer boundaries, including interface placement, constructor injection, and standardized error handling. Use Case: If your Go service has handlers that directly query the database, use this skill to refactor the code to move DB access to the repository layer, define testable interfaces in the handler, and follow standardized wiring and test patterns.

Quick Start

Use the golang-mvc skill to refactor your existing Go service to enforce proper MVC layer boundaries and eliminate cross-layer dependency violations.