How do I install the Solid Go skill?

Run npx skillmds@latest add fusengine/solid-go in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Solid Go safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Solid Go?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Solid Go free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Solid Go?

fusengine (@fusengine) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Solid Go by fusengine — Agent Skill

Name: Solid Go
Rating: 4.2 (5 reviews)
Author: fusengine

File contents

Before writing any new code it requires a DRY check against internal/core/services and internal/core/ports. See solid-principles.md for the overview, the per-principle references for SRP/OCP/LSP/ISP/DIP detail, architecture-patterns.md for hexagonal/modular layout, and the templates for module/service/interface/handler/error/test scaffolding.

SOLID Go - Modular Architecture

Agent Workflow (MANDATORY)

Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:

fuse-ai-pilot:explore-codebase - Analyze existing architecture
fuse-ai-pilot:research-expert - Verify Go docs via Context7
fuse-ai-pilot:sniper - Post-implementation validation

DRY - Reuse Before Creating (MANDATORY)

Before writing ANY new code:

Grep the codebase for similar interfaces, services, or logic
Check shared locations: internal/core/services/, internal/core/ports/
If similar code exists -> extend/reuse instead of duplicate
If code will be used by 2+ features -> create it in internal/core/

Architecture (Modules MANDATORY)

Layer	Location	Max Lines
Handlers	`internal/modules/[feature]/handlers/`	50
Services	`internal/modules/[feature]/services/`	100
Repositories	`internal/modules/[feature]/repositories/`	100
Ports (interfaces)	`internal/modules/[feature]/ports/`	30
Models	`internal/modules/[feature]/models/`	50
Shared	`internal/core/{services,ports,models}/`	-

NEVER use flat internal/ structure - always internal/modules/[feature]/

Critical Rules (MANDATORY)

Rule	Value
File limit	100 lines (split at 90)
Handlers	< 50 lines, delegate to services
Interfaces	`ports/` directory ONLY
Godoc	Every exported function documented
Accept interfaces	Return structs
Small interfaces	1-3 methods max (Go idiom)

Reference Guide

Concepts

Topic	Reference	When to consult
SOLID Overview	solid-principles.md	Quick reference
SRP	single-responsibility.md	Fat structs
OCP	open-closed.md	Adding providers
LSP	liskov-substitution.md	Contracts
ISP	interface-segregation.md	Fat interfaces
DIP	dependency-inversion.md	Injection
Architecture	architecture-patterns.md	Hex/modular

Templates

Template	When to use
module.md	Feature module structure
service.md	Business logic service
interface.md	Port definition
handler.md	HTTP handler
error.md	Custom errors
test.md	Table-driven tests

Forbidden

Anti-Pattern	Fix
Files > 100 lines	Split at 90
Interfaces in impl files	Move to `ports/` directory
Fat interfaces (4+ methods)	Split into small interfaces
Flat `internal/` structure	Use `internal/modules/[feature]/`
`init()` for dependency wiring	Use constructor injection

---name: solid-godescription: Use when writing or refactoring Go code, structuring internal/modules/[feature]/ layers, or defining ports/ interfaces (SOLID, files < 100 lines).---<objective>SOLID Go enforces a modular architecture for Go 1.23+: every feature lives under `internal/modules/[feature]/` (handlers, services, repositories, ports, models) with shared code in `internal/core/`, interfaces (ports) live only in `ports/` directories and stay small (1-3 methods, the Go idiom), functions accept interfaces but return structs, and every exported function carries a godoc comment.Before writing any new code it requires a DRY check against `internal/core/services` and `internal/core/ports`. See `solid-principles.md` for the overview, the per-principle references for SRP/OCP/LSP/ISP/DIP detail, `architecture-patterns.md` for hexagonal/modular layout, and the templates for module/service/interface/handler/error/test scaffolding.</objective># SOLID Go - Modular Architecture## Agent Workflow (MANDATORY)Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:1. **fuse-ai-pilot:explore-codebase** - Analyze existing architecture2. **fuse-ai-pilot:research-expert** - Verify Go docs via Context73. **fuse-ai-pilot:sniper** - Post-implementation validation---## DRY - Reuse Before Creating (MANDATORY)**Before writing ANY new code:**1. **Grep the codebase** for similar interfaces, services, or logic2. Check shared locations: `internal/core/services/`, `internal/core/ports/`3. If similar code exists -> extend/reuse instead of duplicate4. If code will be used by 2+ features -> create it in `internal/core/`---## Architecture (Modules MANDATORY)| Layer | Location | Max Lines ||-------|----------|-----------|| Handlers | `internal/modules/[feature]/handlers/` | 50 || Services | `internal/modules/[feature]/services/` | 100 || Repositories | `internal/modules/[feature]/repositories/` | 100 || Ports (interfaces) | `internal/modules/[feature]/ports/` | 30 || Models | `internal/modules/[feature]/models/` | 50 || Shared | `internal/core/{services,ports,models}/` | - |**NEVER use flat `internal/` structure - always `internal/modules/[feature]/`**---## Critical Rules (MANDATORY)| Rule | Value ||------|-------|| File limit | 100 lines (split at 90) || Handlers | < 50 lines, delegate to services || Interfaces | `ports/` directory ONLY || Godoc | Every exported function documented || Accept interfaces | Return structs || Small interfaces | 1-3 methods max (Go idiom) |---## Reference Guide### Concepts| Topic | Reference | When to consult ||-------|-----------|-----------------|| **SOLID Overview** | [solid-principles.md](references/solid-principles.md) | Quick reference || **SRP** | [single-responsibility.md](references/single-responsibility.md) | Fat structs || **OCP** | [open-closed.md](references/open-closed.md) | Adding providers || **LSP** | [liskov-substitution.md](references/liskov-substitution.md) | Contracts || **ISP** | [interface-segregation.md](references/interface-segregation.md) | Fat interfaces || **DIP** | [dependency-inversion.md](references/dependency-inversion.md) | Injection || **Architecture** | [architecture-patterns.md](references/architecture-patterns.md) | Hex/modular |### Templates| Template | When to use ||----------|-------------|| [module.md](references/templates/module.md) | Feature module structure || [service.md](references/templates/service.md) | Business logic service || [interface.md](references/templates/interface.md) | Port definition || [handler.md](references/templates/handler.md) | HTTP handler || [error.md](references/templates/error.md) | Custom errors || [test.md](references/templates/test.md) | Table-driven tests |---## Forbidden| Anti-Pattern | Fix ||--------------|-----|| Files > 100 lines | Split at 90 || Interfaces in impl files | Move to `ports/` directory || Fat interfaces (4+ methods) | Split into small interfaces || Flat `internal/` structure | Use `internal/modules/[feature]/` || `init()` for dependency wiring | Use constructor injection |

Frequently asked questions

Solid Go