go-backend-guidelines

Guide Go Echo backend development with layered architecture and sqlc.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/NoahYn/climb.com --skill go-backend-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-backend-guidelines
Source: https://github.com/NoahYn/climb.com/tree/main/.claude/skills/go-backend-guidelines
Command: npx skills add https://github.com/NoahYn/climb.com --skill go-backend-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive set of guidelines and best practices for developing Go backends, ensuring consistency, maintainability, and efficiency across the climb.com platform.

Core Features & Use Cases

  • Standardized Project Structure: Enforces a clear and organized directory layout for backend services.
  • Layered Architecture: Guides the implementation of Handler, Service, and Repository layers for modularity.
  • Tooling Integration: Details the use of sqlc for type-safe SQL, golang-migrate for schema versioning, and Echo framework for APIs.
  • Use Case: When starting a new Go backend feature, consult this Skill to understand the correct way to structure handlers, services, database queries, and migrations, ensuring adherence to climb.com's established patterns.

Quick Start

Follow the project structure outlined in this guide when creating new API endpoints or backend features.

Frequently Asked Questions about go-backend-guidelines

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

FAQPage Schema
How do I structure a Go backend using Echo and sqlc?

Structure a Go backend using Echo and sqlc by adopting a layered architecture with distinct Handler, Service, and Repository layers. This enforces modularity, standardizes the project directory layout, and ensures maintainability across backend services.

What is the best way to manage database schema versioning in a Go backend?

The best way to manage database schema versioning in a Go backend is using golang-migrate. It provides reliable schema evolution alongside type-safe SQL generation, ensuring database queries remain consistent and maintainable during API endpoint creation.

How do I implement type-safe SQL queries in a Go Echo application?

Implement type-safe SQL queries in a Go Echo application by integrating sqlc. It compiles SQL into type-safe Go code, working seamlessly within the Repository layer to handle database queries efficiently without runtime mapping errors.

Can I use this layered architecture guide for existing Go backend features?

Yes, you can use this layered architecture guide for existing Go backend features. It provides standards to refactor handlers, services, and database queries, ensuring they adhere to established patterns and REST API conventions.

How do I set up middleware in a Go Echo backend?

Set up middleware in a Go Echo backend by following the established REST API conventions and project structure guidelines. This ensures modular configuration of cross-cutting concerns within the Handler layer for consistent request processing.