- Home
- Skills
- APIs & Backend
- Food Delivery Microservices Platform
Works with the AI Agents you already use
Food Delivery Microservices Platform
Production-grade Go microservices toolkit for Clean Architecture, Echo, GORM, and RabbitMQ messaging.
$19
Food Delivery Microservices Platform
Example session with this skill installed
Add a new endpoint to the order-service for cancelling an order. It should update the status in Postgres and follow the unified response format.
- Read your context and instructions
- Compiled the food delivery microservices
I have implemented the order cancellation endpoint in the order-service following Clean Architecture patterns. This includes updating the domain interfaces, the GORM repository implementation, the usecase logic with state validation, and the Echo HTTP handler with the unified response envelope.
Order Cancellation Implementation
Domain Layer (internal/domain/order.go)
type CancelOrderRequest struct {
Reason string `json:"reason" validate:"required"`
}
type OrderRepository interface {
UpdateStatus(ctx context.Context, id string, status string) error
}
type OrderUsecase interface {
CancelOrder(ctx context.Context, id string, req *CancelOrderRequest) error
}
Usecase Layer (internal/usecase/order_usecase.go)
func (u *orderUsecase) CancelOrder(ctx context.Context, id string, req *domain.CancelOrderRequest) error {
order, err := u.repo.GetByID(ctx, id)
if err != nil {
return err
}
if order.Status == "COMPLETED" || order.Status == "DELIVERING" {
return errors.New("cannot cancel an order that is delivering or already completed")
}
return u.repo.UpdateStatus(ctx, order.ID, "CANCELED")
}
HTTP Delivery (internal/delivery/http/order_handler.go)
func (h *OrderHandler) CancelOrder(c echo.Context) error {
orderID := c.Param("id")
var req domain.CancelOrderRequest
if err := c.Bind(&req); err != nil {
return c.JSON(http.StatusBadRequest, domain.APIResponse{
Success: false,
Message: "Invalid request payload",
Error: err.Error(),
})
}
err := h.usecase.CancelOrder(c.Request().Context(), orderID, &req)
if err != nil {
return c.JSON(http.StatusBadRequest, domain.APIResponse{
Success: false,
Message: "Failed to cancel order",
Error: err.Error(),
})
}
return c.JSON(http.StatusOK, domain.APIResponse{
Success: true,
Message: "Order cancelled successfully",
Data: map[string]string{"order_id": orderID, "status": "CANCELED"},
})
}
Next steps
- Register the
POST /api/v1/orders/:id/cancelroute in your router setup. - Run the service and verify the endpoint appears in the root
postman_collection.json. - Add a RabbitMQ publisher in the usecase if other services need to react to cancellations.
Connects securely to your tools. The creator never sees your data.
About this skill
This package provides a standardized toolset for developing and maintaining a production-grade Go microservices ecosystem. It solves the fragmentation common in distributed systems by enforcing Clean Architecture, unified API response formats, and reliable event-driven communication protocols. Developers can maintain architectural integrity across multiple services while automating repetitive scaffolding and integration tasks.
What it does
- Scaffold Microservices using a standardized directory layout with Echo, GORM, and RabbitMQ.
- Implement REST Endpoints following strict Clean Architecture guardrails from domain to delivery layers.
- Orchestrate Event Workflows using RabbitMQ topic exchanges for reliable asynchronous service communication.
- Sync Postman Collections automatically by updating environment-aware request templates and test assertions.
How it works
- Initialize a new service with pre-configured Docker, GORM, and RabbitMQ boilerplate.
- Define Domain Contracts using context-aware interfaces and DTOs to ensure business logic remains pure.
- Connect Infrastructure by implementing GORM repository queries and Echo handlers that return unified JSON envelopes.
- Wire Events by configuring background consumers and publishers with persistent delivery modes.
Frameworks & tools
Built for Go 1.21+ using Echo v4, GORM, PostgreSQL 15, RabbitMQ 3.12, and Docker multi-stage builds.
Why this beats prompting it yourself
Manual prompting often misses critical microservice patterns like context propagation, unified error envelopes, and durable event acknowledgments. This skill enforces these production standards across every layer, preventing architectural drift and ensuring services remain compatible.
Use cases
- Generating a new service with full dependency injection and graceful shutdown logic.
- Adding a new validated REST endpoint to an existing service within the platform.
- Implementing a reliable event publisher-consumer pair between order and payment services.
- Maintaining an up-to-date Postman collection for an evolving API surface.
Known limitations
Does not support cross-database queries or non-relational database drivers. Assumes a specific folder structure for Clean Architecture compliance.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Requires Go 1.21+ and Docker. Restricted to Clean Architecture patterns. No support for cross-service joins or non-PostgreSQL databases.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 19 days ago