goddd

Guide Go teams to implement hexagonal architecture with GoDDD patterns.

42|2|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/ixugo/goddd --skill goddd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goddd
Source: https://github.com/ixugo/goddd/tree/main/.cursor/skills/goddd
Command: npx skills add https://github.com/ixugo/goddd --skill goddd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GoDDD hexagonal architecture provides a blueprint to build modular, testable Go services with clear domain boundaries and decoupled adapters.

Core Features & Use Cases

  • Hexagonal architecture guidance for API, Core, and Store layering to improve maintainability and testability.
  • godddx code generation workflow to scaffold domain entities, ports, adapters, and wiring.
  • Techniques for cross-domain integration, WithContext usage, and consistent CRUD scaffolding.

Quick Start

Scaffold a new domain with godddx, wire the API, core, and store components, then run and test.

Frequently Asked Questions about goddd

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

FAQPage Schema
How do I implement hexagonal architecture in a Go backend project?

You implement hexagonal architecture in a Go backend by enforcing clean domain boundaries, adapter-driven integration, and deterministic CRUD scaffolding across API, Core, and Store layers. This approach decouples adapters to improve service maintainability and testability.

What is the best way to scaffold domain entities and ports in Go?

The best way to scaffold domain entities and ports is using the godddx code generation workflow. It generates domain entities, ports, adapters, and wiring to ensure consistent parameter and sorting implementations across your modular architecture.

How does port and adapter separation improve Go services?

Port and adapter separation improves Go services by decoupling core domain logic from external integrations. This hexagonal architecture pattern provides a blueprint to build modular, testable services with clear domain boundaries and deterministic CRUD scaffolding.

Can I use GoDDD for cross-domain integration and context propagation in Go?

Yes, you can use GoDDD for cross-domain integration and context propagation in Go. It provides techniques for WithContext usage and adapter-driven integration to maintain clean domain boundaries across API, Core, and Store layers.

When do I need hexagonal architecture for my Go services?

You need hexagonal architecture for Go services when your project requires clean domain boundaries, adapter-driven integration, and deterministic CRUD scaffolding. It solves the complexity of modular architecture by decoupling adapters to improve maintainability and testability.