zero-skills

Generate and review go-zero microservice code with REST, RPC, and database patterns.

4|Updated May 17, 2026
One-click install
npx skills add https://github.com/hellopoisonx/aim --skill zero-skills-hellopoisonx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zero-skills
Source: https://github.com/hellopoisonx/aim/tree/main/skills/zero-skills
Command: npx skills add https://github.com/hellopoisonx/aim --skill zero-skills-hellopoisonx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you build correct, production-ready go-zero microservices by providing ready-to-use patterns for REST APIs, RPC services, database/model integration, resilience, and troubleshooting.

Core Features & Use Cases

  • go-zero architecture guidance: Enforces Handler → Logic → Model separation with ServiceContext dependency injection, including common anti-pattern avoidance.
  • Implementation-ready patterns: Covers REST and gRPC workflows, middleware/validation/error handling, SQL model generation patterns, and retry/circuit breaker/rate limiting/load shedding guidance.
  • Operational troubleshooting: Helps diagnose frequent go-zero issues such as goctl generation errors, config problems, runtime failures, and RPC discovery/timeouts.

Quick Start

Ask your AI assistant to create a REST API service using go-zero with CRUD endpoints, middleware (e.g., auth), database models generated via goctl, and production resilience patterns.

Frequently Asked Questions about zero-skills

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

FAQPage Schema
How do I generate production-ready go-zero microservices using goctl?

Generate go-zero microservices by defining API and proto files, then use goctl to scaffold the structured Handler, Logic, and Model layers. This enforces ServiceContext dependency injection and applies production-ready resilience patterns for REST and gRPC workflows.

What is the correct architecture for a go-zero REST API service?

The correct go-zero architecture requires a strict three-layer separation: Handler, Logic, and Model. ServiceContext handles dependency injection to connect these layers, ensuring clean boundaries while avoiding common anti-patterns in REST API development.

How do I add resilience patterns like circuit breakers and rate limiting in go-zero?

Add resilience patterns in go-zero by applying built-in guardrails for circuit breakers, rate limiting, load shedding, and retries. These mechanisms harden microservices against runtime failures and ensure stable operation under high traffic loads.

Can I use this to troubleshoot goctl generation errors and RPC timeouts?

Yes, you can troubleshoot frequent go-zero issues including goctl generation errors, configuration loading problems, runtime failures, and RPC discovery or timeout errors. It provides operational guidance to diagnose and resolve these common microservice issues.

How do I generate database models from SQL using goctl in a go-zero project?

Generate database models using goctl by applying prescribed SQL model generation patterns within the Model layer. This integrates seamlessly with the ServiceContext to provide structured data access for your REST and gRPC services.