initium-backend

Implement Go backend changes under backend/ with hexagonal architecture and OpenAPI contracts.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/CaDs/initium --skill initium-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: initium-backend
Source: https://github.com/CaDs/initium/tree/main/.claude/skills/initium-backend
Command: npx skills add https://github.com/CaDs/initium --skill initium-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers in writing or modifying the Go backend for the Initium starter template, ensuring adherence to hexagonal architecture, error-envelope conventions, and a code-first OpenAPI workflow.

Core Features & Use Cases

  • Guides structure and project layout for backend components (internal/domain, service, handler, persistence, migrations, and infra) in the Initium fork.
  • Enforces gates like preflight checks, API parity, and consistent repository patterns to keep PR quality high.
  • Provides structured workflow for generating and validating OpenAPI contracts from Go code.

Quick Start

Edit or create backend components under backend/ as directed by this skill and run make preflight to validate gates before PR submission.

Frequently Asked Questions about initium-backend

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

FAQPage Schema
How do I structure a Go backend using hexagonal architecture?

Hexagonal architecture in Go separates domain logic from infrastructure by organizing code into internal/domain, service, handler, and persistence layers. This Skill guides structuring backend components to enforce that separation of concerns within your Initium fork.

How do I generate an OpenAPI contract from Go code using Huma?

Generating an OpenAPI contract from Go code with Huma involves defining operations in your handlers that the framework automatically documents. This Skill provides a structured workflow for validating your Huma-driven OpenAPI definitions against your backend/api/openapi.yaml file.

What are preflight gates and API parity checks in backend development?

Preflight gates and API parity checks are automated validation steps ensuring your Go code matches the OpenAPI contract and meets repository hygiene rules. This Skill enforces these gates so you can run make preflight and validate pull request readiness before submission.

How do I implement error-envelope conventions in a Go API?

Implementing error-envelope conventions in a Go API requires standardizing error responses into a consistent JSON structure across all handlers. This Skill enforces those conventions within the Initium backend, ensuring error responses align with the Huma-driven OpenAPI workflow.

Can I use this Skill for backend migrations in an existing Initium fork?

Yes, you can use this Skill to identify and implement changes to backend migrations under backend/migrations/**. It ensures your database schema changes comply with the preflight gates and repository hygiene rules required for pull request readiness in the Initium fork.

Why does my Go backend PR fail preflight checks?

Go backend pull requests fail preflight checks when code violates hexagonal architecture boundaries, error-envelope conventions, or API parity between handlers and openapi.yaml. This Skill enforces these rules to guide your modifications and ensure compliance before validation.