go-backend

Standardize Go backend patterns for LLMProxy HTTP handlers and middleware.

14|4|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/aiyuekuang/LLMProxy --skill go-backend-aiyuekuang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-backend
Source: https://github.com/aiyuekuang/LLMProxy/tree/main/.windsurf/skills/go-backend
Command: npx skills add https://github.com/aiyuekuang/LLMProxy --skill go-backend-aiyuekuang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go backend development for LLMProxy often lacks consistent patterns, reliable error handling, and performance-oriented guidance. This skill provides pragmatic Go backend practices tailored for building reliable proxy services and HTTP handlers.

Core Features & Use Cases

  • Standard Handler Patterns: Structuring HTTP handlers with validation, business logic, and consistent responses.
  • Middleware & Routing: Reusable middleware for logging, recovery, auth, and rate limiting.
  • Error Handling & Logging: Centralized error types and structured logging to simplify debugging in production.
  • Database & Transactions: Repositories and transactional patterns for safe data operations.
  • Performance Best Practices: Connection pooling, context timeouts, and object pooling for throughput.
  • Testing Patterns: Unit and integration tests for handlers and services.

Quick Start

Apply these patterns to your Go backend code to implement robust handlers, middleware, and data access for LLMProxy.

Frequently Asked Questions about go-backend

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

FAQPage Schema
How do I structure Go backend handlers for an LLM proxy service?

Go backend handlers for an LLM proxy should follow standardized patterns separating validation, business logic, and consistent responses. This approach ensures reliability and consistency across typical proxy HTTP services.

What are the best practices for error handling and logging in Go proxy backends?

Error handling and logging in Go proxy backends should use centralized explicit error types and structured logging. This simplifies production debugging and enforces reliability across proxy services.

How do I implement middleware for rate limiting and auth in a Go LLM proxy?

Middleware for a Go LLM proxy should be built as reusable components handling logging, recovery, auth, and rate limiting. This standardizes routing and improves handler consistency.

How do I manage database transactions safely in a Go backend proxy?

Database transactions in a Go backend proxy should use repository patterns and safe transactional patterns for data operations. This ensures reliable data access and integrity across proxy services.

How do I optimize Go backend performance for high throughput proxy requests?

Go backend performance for proxy requests is optimized using connection pooling, context timeouts, and object pooling. These patterns maximize throughput and enforce safe resource management.

Do I need specific testing patterns for Go LLM proxy handlers and services?

Yes, Go LLM proxy handlers and services require unit and integration testing patterns. These testing practices validate handler logic and ensure service reliability within the proxy backend.