Claude Code Plugins

Community-maintained marketplace

Feedback

Generates gRPC/HTTP service handlers for go-kratos microservices. Creates service structs, handler methods, and integrates with protobuf definitions. Use when implementing service layer for kratos services.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name kratos-service-layer
description Generates gRPC/HTTP service handlers for go-kratos microservices. Creates service structs, handler methods, and integrates with protobuf definitions. Use when implementing service layer for kratos services.
## How Kratos Service Layer Works

Service Layer Role

Connects transport (gRPC/HTTP) to business logic:

Responsibilities:

  • Handle gRPC/HTTP requests
  • Map proto DTOs to business models (via mapper)
  • Call use case methods
  • Map results back to proto responses
  • Convert business errors to gRPC status codes

Service Struct Pattern

type {Entity}Service struct {
	pb.Unimplemented{Entity}ServiceServer  // Embed unimplemented server
	uc biz.{Entity}UseCase                // Use case dependency
}

Handler Method Pattern

func (s *{Entity}Service) Create{Entity}(ctx context.Context, in *pb.Request) (*pb.Response, error) {
	// 1. Map request to business model
	entity := {Entity}FromRequest(in)

	// 2. Call use case
	result, err := s.uc.Create{Entity}(ctx, entity)
	if err != nil {
		return nil, toServiceError(err)  // Map business error to gRPC error
	}

	// 3. Map result to response
	return &pb.Response{Entity: toProto{Entity}(result)}, nil
}
What would you like to do?
  1. Create service handlers for new entity
  2. Add handler methods to existing service
  3. View handler patterns and examples

Wait for response before proceeding.

| Response | Workflow | |----------|----------| | 1, "create", "new" | `workflows/create-service.md` | | 2, "add", "extend" | `workflows/add-handlers.md` | | 3, "examples", "patterns" | `workflows/view-examples.md` |

After reading the workflow, follow it exactly.

**Core**: handler-pattern.md, service-structure.md, error-mapping.md **Mappers**: mapper-conventions.md | Workflow | Purpose | |----------|---------| | create-service.md | Generate service handlers and mappers | | add-handlers.md | Add methods to existing service | | view-examples.md | Show patterns | Service layer code is correct when: - Service struct embeds Unimplemented{Entity}ServiceServer - Constructor added to service.ProviderSet - Handlers map DTOs via mapper functions - Errors converted to gRPC status codes - All methods have godoc comments - User reminded to run `make generate`