Delegate independent tasks to specialized agents working concurrently with isolated context.
Kratos Mapper
kratos-mapper
Generates bidirectional mapper functions (transformers/converters/adapters) between protobuf DTOs and business domain models for go-kratos services. Creates type-safe conversions with proper field mapping, handles timestamps, enums, optional fields, and pagination metadata transformations. Use wh...
SKILL.md
Full skill instructions
<quick_start>
For an entity, create mappers in internal/service/mapper.go:
// Request → Business Model
func {Entity}FromCreateRequest(req *pb.Create{Entity}Request) *domain.{Entity} {
return &domain.{Entity}{
Name: req.Name,
// Map fields...
}
}
// Business Model → Proto Response
func toProto{Entity}(e *domain.{Entity}) *pb.{Entity} {
return &pb.{Entity}{
Id: e.ID,
Name: e.Name,
// Map fields...
}
}
**Import**: `import "{service}/internal/biz/domain"`
</quick_start>
<mapper_patterns>
Common Mapper Patterns
Request to Business Model:
func {Entity}FromCreateRequest(req *pb.Create{Entity}Request) *domain.{Entity}
func {Entity}FromUpdateRequest(req *pb.Update{Entity}Request, id uint64) *domain.{Entity}
Business Model to Proto:
func toProto{Entity}(e *domain.{Entity}) *pb.{Entity}
func toProto{Entities}(list []*domain.{Entity}) []*pb.{Entity}
List Options:
func NewList{Entities}Options(req *pb.List{Entities}Request) *domain.List{Entities}Options {
return &domain.List{Entities}Options{
Pagination: pagination.OffsetPaginationParams{
Offset: req.Offset,
Limit: req.Limit,
},
}
}
Pagination Meta:
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: uint64 ↔ uint64 (direct)
Strings: string ↔ string (direct)
Timestamps: time.Time ↔ *timestamppb.Timestamp
CreatedAt: timestamppb.New(e.CreatedAt)
Optional Fields: Use pointers
// Business has *string, proto has string
Email: func() string {
if e.Email != nil {
return *e.Email
}
return ""
}()
Enums: Map string to proto enum
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>
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
