go-backend

Enforce Go backend coding standards and Hexagonal Architecture patterns.

1|Updated Mar 10, 2025
One-click install
npx skills add https://github.com/devdavidalonso/cecor --skill go-backend-devdavidalonso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-backend
Source: https://github.com/devdavidalonso/cecor/tree/main/.agent/skills/go-backend
Command: npx skills add https://github.com/devdavidalonso/cecor --skill go-backend-devdavidalonso

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes and enforces technical standards and architectural patterns for the Go backend in the CECOR project, ensuring maintainability, resilience, and consistency.

Core Features & Use Cases

  • Coding Standards: Defines naming conventions for packages, structs, functions, variables, and API endpoints in English.
  • Architectural Guidance: Outlines the Hexagonal Architecture pattern and package structure.
  • Database Best Practices: Provides guidelines for GORM models, database naming conventions, and migrations.
  • External Service Integration: Details best practices for integrating with services like Keycloak.
  • Use Case: New developers joining the CECOR project can use this Skill to quickly understand and adhere to the established Go backend development guidelines, leading to faster onboarding and higher code quality.

Quick Start

Follow the naming conventions and architectural patterns outlined in this skill for all new Go backend development.

Frequently Asked Questions about go-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?

To structure a Go backend with Hexagonal Architecture, isolate core domain logic from external concerns by defining clear ports and adapters. This enforces a specific package structure separating database models, API endpoints, and business rules for maintainability.

What are the best practices for GORM model naming conventions in Go?

GORM model best practices in Go require using English-only naming conventions for all structs, variables, and database objects. This ensures internationalization and maintainability across backend services, standardizing database schema design and migrations consistently.

How do I integrate external services like Keycloak in a Go backend?

Integrate external services like Keycloak in a Go backend by following established architectural integration strategies. Use Hexagonal Architecture adapters to isolate external service connectivity from core domain logic, ensuring system resilience and maintainability.

Do I need to follow English-only naming for Go API endpoints and database schemas?

Yes, you must use English-only naming for Go API endpoints, code elements, and database objects. Adhering to this standard ensures internationalization and long-term maintainability across the entire backend project architecture.

When do I need architectural standards for a Go backend project?

You need architectural standards for a Go backend project when onboarding new developers or scaling development. Enforcing technical standards and patterns ensures consistency, resilience, and higher code quality across the software engineering lifecycle.