Skip to content
go-service-hexagonal logo

Go Service Hexagonal

go-service-hexagonal

Define, review, and scaffold Go service directory structures using hexagonal (ports-and-adapters / “jexagonal”) architecture and Go best practices. Use when creating or refactoring Go services, deciding package boundaries, organizing cmd/internal/api/config/deploy/migrations, or choosing layouts ...

SKILL.md

Full skill instructions

Go Service Hexagonal

Workflow

1) Choose the repo shape

  • Use single-service repo when one deployable dominates the repo.
  • Use multi-binary repo when multiple deployables share a domain and are released together (API + worker + migrator).
  • Use monorepo when many services share tooling but keep each service isolated under <service>/​cmd/<service>-<binary> and <service>/​internal/​....

2) Choose the service kind

  • HTTP REST/​JSON API → use references/​layout-http-rest.md
  • gRPC API → use references/​layout-grpc.md
  • Worker/​consumer/​scheduler/​job → use references/​layout-worker.md
  • CLI (ops tools, admin, local runner) → use references/​layout-cli.md

3) Apply hexagonal (ports-and-adapters) boundaries

  • Put business rules in internal/​domain.
  • Put use cases in internal/​app and define inbound ports in internal/​interface.
  • Define outbound ports (interfaces to DB, queues, HTTP clients) in internal/​adapter.
  • Implement inbound adapters in internal/​interface/​* (primary) and outbound adapters in internal/​adapter/​* (secondary).
  • Choose a settings mode: none (defaults only), env (env-only), or config (env + optional config file via Koanf, env overrides config). Use internal/​interface/​options only for config mode.
  • Perform all wiring in a single composition root: internal/​bootstrap.Compose(...) and keep cmd/​* thin.

Use references/​architecture-rules.md as the dependency rulebook.

4) Refactor an existing project

  • Read references/​refactor-workflow.md.
  • For minimal, necessary tests during refactors, read references/​refactor-testing.md.
  • Create a refactor plan using references/​refactor-plan-template.md and agree on it with the user before making changes.
  • Execute the plan in small, explicit steps and confirm after each step.
  • Track the plan in a checkboxed REFACTORING.md at repo root and mark completed items as you finish them.

Scaffolding

Run the scaffolder to generate a starting tree plus minimal compileable stubs:

python3 scripts/​scaffold_hex_service.py --root <repo> --service <name> --kinds http,worker

Pick a settings mode:

  • Defaults only: --settings none
  • Env only (default): --settings env
  • Env + config file (Koanf): --settings config

Example (config mode):

python3 scripts/​scaffold_hex_service.py --root <repo> --service <name> --kinds http --settings config

Config files (when enabled) support json/​yaml/​toml with keys: http_addr, pprof_addr, pprof_port, log_level. If the config file has no extension, TOML is assumed. Environment values override config values when both are set.

HTTP scaffolding defaults to Echo. For explicit Echo:

python3 scripts/​scaffold_hex_service.py --root <repo> --service <name> --kinds http --http-framework echo

For a pure net/​http baseline:

python3 scripts/​scaffold_hex_service.py --root <repo> --service <name> --kinds http --http-framework nethttp

HTTP scaffolds include GET /​health/​live and GET /​health/​ready, plus request logging using Logrus (github.com/​sirupsen/​logrus).

Optional (opt-in) HTTP debug endpoints:

  • --http-pprof adds handlers under GET /​debug/​pprof/​* (pprof index + profiles).
  • --http-trace adds GET /​debug/​pprof/​trace (execution trace).
  • These run on a separate debug HTTP server and are activated only when PPROF_PORT is set (e.g. PPROF_PORT=6060); optionally set PPROF_ADDR to change the bind address (default 127.0.0.1).
  • The handler mux is scaffolded as a dedicated inbound adapter: internal/​interface/​debughttp.

For new projects, if --module is omitted the module path defaults to the <repo> folder name (no github.com/​... assumption). If go.mod is created (new project), the scaffolder runs go mod tidy to fetch dependencies (Echo + Logrus). Use --skip-deps to skip.

Generated projects include required README.md, AGENTS.md, and Makefile at repo root. When HTTP is scaffolded, the project also includes test/​health_test.go.

Then edit the generated packages to match your domain and ports.

Reference Index

Read references/​index.md and then open only the layout file(s) you need for the chosen service kind.

More skills from majiayu000

xiaohongshu logo
majiayu000/claude-arsenal

xiaohongshu

xiaohongshu

286 148
View
agent-task-conductor logo
majiayu000/claude-skill-registry

agent-task-conductor

Conduct multi-agent task orchestration and workflow coordination.

663 1
View
conductor-setup logo
majiayu000/claude-skill-registry

conductor-setup

Initialize project with Conductor artifacts (product definition,

663 1
View
animation-designer logo
majiayu000/claude-skill-registry

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS

663 1
View
diagramming logo
majiayu000/claude-skill-registry

diagramming

Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...

663 1
View
h3-pg logo
majiayu000/claude-skill-registry-data

h3-pg

PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.

23 1
View
conductor-development logo
majiayu000/claude-skill-registry

conductor-development

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...

663 1
View
conductor-status logo
majiayu000/claude-skill-registry

conductor-status

Display project status, active tracks, and next actions

663 1
View
dockerization logo
majiayu000/claude-skill-registry

dockerization

Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.

663 1
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View