do-proto

Generate Protocol Buffer definitions for a domain and resource.

1|Updated Mar 8, 2026

Search Tags:#code generation #protobuf #grpc #connect-rpc #api contract #service definition

Ready to run

npx skills add https://github.com/viqueen/claude-go-playground --skill do-proto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: do-proto
Source: https://github.com/viqueen/claude-go-playground/tree/main/.claude/skills/do-proto
Command: npx skills add https://github.com/viqueen/claude-go-playground --skill do-proto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Protocol Buffer (Protobuf) definitions, which are essential for defining API contracts and ensuring consistent data structures across different services.

Core Features & Use Cases

Generates Protobuf files: Creates _model.proto, _refs.proto, and _service.proto files based on domain and resource specifications.
Enforces best practices: Includes validation annotations, correct package naming, and standard RPC patterns.
Use Case: When starting a new microservice or adding a new API endpoint, use this Skill to quickly generate the foundational Protobuf definitions, ensuring adherence to project standards.

Quick Start

Use the do-proto skill to define the API contract for a new 'user' domain.

Frequently Asked Questions about do-proto

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

FAQPage Schema

How do I generate Protobuf definitions for a new microservice API?▼

To generate Protobuf definitions, specify your target domain and resource. The system then creates the foundational `_model.proto`, `_refs.proto`, and `_service.proto` files, automatically enforcing API design best practices and project-specific conventions.

What is the best way to structure a Protobuf API contract with CRUD operations?▼

The best way to structure a Protobuf API contract is to separate concerns into model, reference, and service files. This approach cleanly defines CRUD operations, data validation rules, and cross-domain references while adhering to standard RPC patterns.

How does cross-domain referencing work when defining Protocol Buffer service definitions?▼

Cross-domain referencing in Protocol Buffer service definitions works by generating dedicated `_refs.proto` files. These files map relationships between different domains, ensuring consistent data structures and accurate external resource validation across separate microservices.

Can I include data validation rules directly in my generated Protobuf models?▼

Yes, you can include data validation rules in generated Protobuf models. The generation process automatically adds validation annotations to the `_model.proto` files, ensuring data integrity and adherence to specified constraints.

Do I need to manually configure package naming for my gRPC service definitions?▼

No, you do not need to manually configure package naming for gRPC service definitions. The generation process enforces correct package naming and standard RPC patterns automatically, ensuring project-specific conventions are met.