proto-backend-module

Generate Go backend modules from proto definitions for goddess, marksman, and rabbit microservices.

253|64|Updated Jul 22, 2023
One-click install
npx skills add https://github.com/aide-family/moon --skill proto-backend-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proto-backend-module
Source: https://github.com/aide-family/moon/tree/main/.cursor/skills/proto-backend-module
Command: npx skills add https://github.com/aide-family/moon --skill proto-backend-module

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of backend modules by automatically generating code from Protocol Buffer definitions, ensuring consistency and adherence to project conventions.

Core Features & Use Cases

  • Automated Code Generation: Implements backend logic based on proto definitions for goddess, marksman, and rabbit apps.
  • Convention Enforcement: Maintains style consistency, reuses existing code (magicbox, in-app), and follows Go and project conventions.
  • Use Case: When a user requests to implement a new feature like "user authentication module" based on a provided proto file, this Skill will generate the necessary service, biz, and data layers, keeping the codebase clean and maintainable.

Quick Start

Use the proto-backend-module skill to implement the 'order' module based on the provided proto definition.

Frequently Asked Questions about proto-backend-module

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

FAQPage Schema
How do I generate Go backend code from proto definitions?

To generate Go backend code from proto definitions, provide the proto file to trigger automated translation of APIs into functional service, business logic, and data access layers for microservices.

What is the best way to implement microservices in Go using proto files?

The best way to implement Go microservices from proto files is by enforcing project-specific coding standards, promoting shared library reuse like magicbox, and ensuring adherence to Go language conventions.

Does this backend code generation work with goddess, marksman, and rabbit apps?

Yes, backend code generation specifically targets the goddess, marksman, and rabbit microservices, translating proto APIs into functional code while maintaining style consistency across these specific applications.

How do I ensure code reuse from shared libraries when generating backend modules?

To ensure code reuse from shared libraries when generating backend modules, the process automatically enforces convention adherence, reusing existing code from libraries like magicbox and in-app resources during implementation.

Can I generate the data access and biz layers from a proto API definition?

Yes, you can generate the data access and biz layers directly from a proto API definition, facilitating the implementation of new features by translating proto APIs into functional backend code across required layers.