go-microservice-scaffold

Create a Go microservice scaffold with a standard directory structure.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/333-333-333/agents --skill go-microservice-scaffold
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: go-microservice-scaffold
Source: https://github.com/333-333-333/agents/tree/main/skills/go-microservice-scaffold
Command: npx skills add https://github.com/333-333-333/agents --skill go-microservice-scaffold

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Scaffold a production-ready Go microservice with a standard, scalable directory structure to reduce boilerplate and accelerate delivery.

Core Features & Use Cases

  • Standard Go project layout under api/, including cmd/, internal/, proto/, migrations, and infrastructure.
  • Supports single-domain and multi-domain service patterns with clear domain placement and wiring notes.
  • Quick adaptation path for creating new services and adding domains with consistent conventions.

Quick Start

Run the scaffold to initialize the api/{service} directory with a conventional module and starter files.

Frequently Asked Questions about go-microservice-scaffold

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

FAQPage Schema
How do I scaffold a Go microservice with a standard directory structure?▼

To scaffold a Go microservice, this tool generates a production-ready directory layout including api/, cmd/, internal/, proto/, migrations, and infrastructure folders. It enforces conventional module setup and creates a composition root in cmd/server/main.go for immediate bootstrapping of new services.

What is the conventional project layout for a scalable Go microservice?▼

A conventional Go microservice layout separates concerns across api/, cmd/, internal/, proto/, migrations, and infrastructure directories. This standard structure reduces boilerplate, enforces clear domain placement, and accelerates delivery by providing consistent conventions for single-domain and multi-domain service patterns.

Can I use this scaffold to add a new domain to an existing Go microservice?▼

Yes, you can use this scaffold to add domains to an existing Go microservice. It supports both single-domain and multi-domain service patterns by providing clear domain placement and wiring notes, ensuring consistent conventions when expanding your service architecture.

How do I bootstrap a new Go server using a microservice scaffold?▼

Bootstrapping a new Go server involves running the scaffold to initialize the api/{service} directory with a conventional module and starter files. The composition root is established in cmd/server/main.go, allowing easy wiring and quick adaptation for creating new services.

Does this Go microservice scaffold include infrastructure and database migration layouts?▼

Yes, the Go microservice scaffold includes both infrastructure layout and database migrations directories. It creates a comprehensive directory structure encompassing api/, cmd/, internal/, proto/, and migrations to ensure production-ready architecture and scalable domain wiring.

What is the best way to reduce boilerplate when creating new Go microservices?▼

The best way to reduce boilerplate is using a scaffold that enforces a standard, scalable directory structure for Go microservices. By generating conventional module setups, domain placements, and a composition root automatically, it accelerates delivery and eliminates repetitive project initialization tasks.