Agent skill

kratos-mapper

Generates bidirectional mapper functions between protobuf DTOs and business models for go-kratos services. Creates type-safe conversions with proper field mapping. Use when implementing service layer mappers.

Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/kratos-mapper

SKILL.md

<quick_start> For an entity, create mappers in internal/service/mapper.go:

go
// Request → Business Model
func {Entity}FromCreateRequest(req *pb.Create{Entity}Request) *biz.{Entity} {
	return &biz.{Entity}{
		Name: req.Name,
		// Map fields...
	}
}

// Business Model → Proto Response
func toProto{Entity}(e *biz.{Entity}) *pb.{Entity} {
	return &pb.{Entity}{
		Id:   e.ID,
		Name: e.Name,
		// Map fields...
	}
}

</quick_start>

<mapper_patterns>

Common Mapper Patterns

Request to Business Model:

go
func {Entity}FromCreateRequest(req *pb.Create{Entity}Request) *biz.{Entity}
func {Entity}FromUpdateRequest(req *pb.Update{Entity}Request, id uint64) *biz.{Entity}

Business Model to Proto:

go
func toProto{Entity}(e *biz.{Entity}) *pb.{Entity}
func toProto{Entities}(list []*biz.{Entity}) []*pb.{Entity}

List Options:

go
func NewList{Entities}Options(req *pb.List{Entities}Request) *biz.List{Entities}Options {
	return &biz.List{Entities}Options{
		Pagination: pagination.PaginationParams{
			Offset: req.Offset,
			Limit:  req.Limit,
		},
	}
}

Pagination Meta:

go
func toProtoPaginationMeta(meta *pagination.PaginationMeta) *pb.PaginationMeta {
	return &pb.PaginationMeta{
		Total:  meta.Total,
		Offset: meta.Offset,
		Limit:  meta.Limit,
	}
}

</mapper_patterns>

<naming_conventions>

Naming Rules

Proto → Business: {Entity}From{Operation}Request

  • Example: SymbolFromCreateRequest, ProductFromUpdateRequest

Business → Proto: toProto{Entity} or toProto{Entities}

  • Example: toProtoSymbol, toProtoSymbols

Options: NewList{Entities}Options

Helpers: toProto{Type} for common types

  • Example: toProtoPaginationMeta, toProtoTimestamp </naming_conventions>

<type_conversions>

Common Type Conversions

IDs: uint64uint64 (direct) Strings: stringstring (direct) Timestamps: time.Time*timestamppb.Timestamp

go
CreatedAt: timestamppb.New(e.CreatedAt)

Optional Fields: Use pointers

go
// Business has *string, proto has string
Email: func() string {
	if e.Email != nil {
		return *e.Email
	}
	return ""
}()

Enums: Map string to proto enum

go
Status: pb.Status(pb.Status_value[e.Status])

</type_conversions>

<file_organization>

Where to Put Mappers

Single entity: internal/service/mapper.go (all mappers) Multiple entities: internal/service/{entity}_mapper.go (per entity)

Keep mapper functions close to service handlers for easy reference. </file_organization>

<success_criteria> Mapper functions are correct when:

  • Naming follows conventions ({Entity}From* vs toProto*)
  • All proto fields mapped to business model fields
  • Type conversions handled (timestamps, optionals, enums)
  • Nil checks for optional/pointer fields
  • List mappers use range loops
  • Pagination helpers created if needed
  • Functions are pure (no side effects) </success_criteria>

Didn't find tool you were looking for?

Be as detailed as possible for better results