go-database

Implement Go service database layers with clean architecture standards.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/kabradshaw1/go-standards --skill go-database-kabradshaw1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-database
Source: https://github.com/kabradshaw1/go-standards/tree/main/skills/go-database
Command: npx skills add https://github.com/kabradshaw1/go-standards --skill go-database-kabradshaw1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires DBInterface, types, service, client, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The go-database skill simplifies the process of implementing or reviewing the database layer for Go services, following architecture standards, and reduces the time to create and maintain consistent and clean database access.

Core Features & Use Cases

  • Database Implementation Guidance: Provides instructions and standards for the database layer.
  • Code Layout Structure: Describes the recommended directory structure for a clean-architecture database implementation.
  • Layer Build Order: Outlines the required build order to maintain clean code separation between layers.
  • Error Handling Standards: Specifies how to handle configuration errors and logging for recoverable errors.

Quick Start

Execute the 'go-standards go-database' command followed by your service name to initiate the implementation or review process.

Frequently Asked Questions about go-database

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

FAQPage Schema
How do I implement the database layer for a Go service following clean architecture?

Implementing the database layer for a Go service requires managing dependencies on 'types', 'service', and 'client' layers. It enforces a 'Connect' function to ensure successful connections before handling data access operations.

What is the required build order for a clean architecture Go service database layer?

The required build order maintains strict code separation between layers. You must handle data access operations only after successfully enforcing the 'Connect' function to establish database connectivity.

How should I handle configuration errors and logging in a Go database access layer?

Handle configuration errors and logging for recoverable errors in a Go database access layer according to specified architecture standards. This ensures consistent and clean database access across the service.

What directory structure is recommended for a clean architecture Go service database implementation?

A clean architecture Go service database implementation recommends a specific code layout structure that standardizes data access operations. It separates dependencies like 'types', 'service', and 'client' layers effectively.

Can I use this approach to review an existing Go database layer for architecture compliance?

Yes, you can review an existing Go database layer for architecture compliance. The process initiates a review mode to check data access operations, layer dependencies, and error handling standards against your service name.