gold-arch

Guide Go developers in applying layered architecture for microservices.

6|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/vmkteam/claude-plugins --skill gold-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gold-arch
Source: https://github.com/vmkteam/claude-plugins/tree/main/plugins/developer/skills/gold-arch
Command: npx skills add https://github.com/vmkteam/claude-plugins --skill gold-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gold Architecture provides a clear, durable blueprint for designing Go services using a layered architecture, reducing integration risk and onboarding time.

Core Features & Use Cases

  • Layered architecture guidance for api, domain, and db boundaries with explicit package conventions.
  • Codegen and tooling conventions (mfd-generator, zenrpc, colgen) to minimize boilerplate and drift.
  • Onboarding and scale-ready patterns for large teams building production Go services.

Quick Start

Consult this guide when designing a new Go service to apply the recommended layered architecture and conventions.

Frequently Asked Questions about gold-arch

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

FAQPage Schema
What is the best way to structure a Go microservice with API, domain, and DB boundaries?

A layered architecture is the best way to structure Go microservices, enforcing explicit package conventions for API, domain, and DB boundaries to reduce integration risk and onboarding time.

How do I minimize boilerplate and code drift when generating Go microservice code?

To minimize boilerplate and code drift in Go microservices, apply disciplined codegen and tooling conventions using tools like mfd-generator, zenrpc, rpcgen, and colgen to ensure consistency.

How does a layered architecture improve large team Go service development?

A layered architecture improves large team Go service development by providing a durable blueprint with explicit package conventions and module layouts, which significantly reduces onboarding time and integration risk.

Does this Go service architecture guide require specific tools for code generation?

Yes, this Go service architecture guide requires specific codegen tools including mfd-generator, zenrpc, rpcgen, and colgen to enforce naming conventions, module layout, and a disciplined toolchain for production-ready services.

When do I need a layered architecture pattern for my Go production services?

You need a layered architecture pattern for Go production services when building microservices that require strict API, domain, and DB boundaries alongside codegen and observability requirements for maintainability at scale.