clean-feature-delivery

Implement features within a clean-architecture boundary across Go service layers.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/cuenobi/golang-clean --skill clean-feature-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-feature-delivery
Source: https://github.com/cuenobi/golang-clean/tree/main/.cursor/skills/clean-feature-delivery
Command: npx skills add https://github.com/cuenobi/golang-clean --skill clean-feature-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement or refactor features within a disciplined clean-architecture approach to reduce coupling, improve testability, and simplify maintenance across Go services.

Core Features & Use Cases

  • Enforce a merged-layer style (application, domain, interfaces, infrastructure) to avoid per-module duplicated infrastructure.
  • Define clear responsibilities per layer: domain invariants, application orchestration, interfaces/http DTOs and mappers, and infrastructure persistence implementations.
  • Use Case: When delivering a new feature, apply the pattern to keep modules cohesive and replaceable while staying aligned with project rules.

Quick Start

Outline the next feature with per-layer module boundaries and implement domain, application, interfaces, and infrastructure components accordingly.

Frequently Asked Questions about clean-feature-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Go project using clean architecture for feature delivery?

Structure a Go project using clean architecture by separating features into domain, application, interfaces/http, and infrastructure layers. This reduces coupling, improves testability, and simplifies maintenance by enforcing clear module boundaries and cohesive use cases.

What is the best way to organize Golang modules to avoid duplicated infrastructure?

Organize Golang modules by enforcing a merged-layer style across application, domain, interfaces, and infrastructure. This prevents per-module infrastructure duplication while keeping modules cohesive, replaceable, and aligned with project rules.

How do I implement domain invariants and use cases in a clean architecture Golang service?

Implement domain invariants in the domain layer and use case orchestration in the application layer. This clean architecture separation ensures cohesive use cases, robust boundaries, and deterministic tests while satisfying validation and UTC timestamp requirements.

Does applying DDD and clean architecture in Go help with refactoring existing features?

Applying DDD and clean architecture helps refactor existing Go features by establishing disciplined boundaries. It reduces coupling, improves testability, and simplifies maintenance by defining clear responsibilities across domain, application, interfaces, and infrastructure layers.

When should I use a layered clean architecture approach for delivering Go features?

Use a layered clean architecture approach when delivering new Go features requiring high maintainability and testability. It keeps modules cohesive and replaceable while satisfying requirements for layered separation, validation, UTC timestamps, and deterministic tests.