r2mo-rad-domain

Translate protobuf model names and append Chinese semantic constraints to fields.

2|1|Updated Nov 20, 2025

Search Tags:#automation #localization #protobuf #code-quality #domain-model #semantic-commenting

Ready to run

npx skills add https://github.com/silentbalanceyh/r2mo-lain --skill r2mo-rad-domain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: r2mo-rad-domain
Source: https://github.com/silentbalanceyh/r2mo-lain/tree/main/skills/r2mo-rad-domain
Command: npx skills add https://github.com/silentbalanceyh/r2mo-lain --skill r2mo-rad-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain protobuf models often lack semantic clarity and consistent naming, hindering maintenance and integration. This Skill translates model names into business-relevant Chinese and augments definitions with field-level constraints, improving readability and governance.

Core Features & Use Cases

Translate main model names into concise business Chinese and append as comments to the message definitions.
Infer and attach semantic constraints to fields (e.g., email, price, date) based on common patterns.
In-place enhancement of .proto files located under {PROJECT_ID}-ui/.r2mo/domain/ for downstream tooling.

Quick Start

Process your project's protobuf domain files under {PROJECT_ID}-ui/.r2mo/domain/ to append Chinese semantic comments and field constraints.

Frequently Asked Questions about r2mo-rad-domain

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

FAQPage Schema

How do I add Chinese semantic comments to protobuf domain models?▼

To add Chinese semantic comments to protobuf domain models, you can use an AI-driven approach that translates main model names into business Chinese and appends field-level constraints to your .proto files. This process enhances readability and governance for downstream tooling.

What are semantic constraints in protobuf field definitions?▼

Semantic constraints in protobuf fields are descriptive annotations inferred from field names like email, price, created_at, and id. They provide business context and validation rules directly within the .proto file syntax to improve model clarity and maintenance.

Can I automatically annotate protobuf fields based on naming patterns?▼

Yes, you can automatically annotate protobuf fields based on naming patterns by processing .proto files in-place. The mechanism derives constraints from common field names like email or date, appending descriptive Chinese comments while preserving the original package and types.

Does this protobuf annotation approach work with Java Maven projects?▼

Yes, this protobuf annotation approach works with Java Maven projects. It requires a pom.xml file and processes .proto files located specifically within the {PROJECT_ID}-ui/.r2mo/domain/ directory structure for in-place enhancement.

Will in-place rewriting of .proto files preserve my existing syntax and types?▼

In-place rewriting of .proto files preserves your existing syntax, package declarations, and types. The process safely appends Chinese semantic comments and derived field constraints without altering the original structure or breaking downstream integration.

Why do domain protobuf models need business Chinese translations?▼

Domain protobuf models need business Chinese translations to solve the problem of lacking semantic clarity. Translating main model names and appending field constraints improves readability, governance, and maintenance for teams working with localized domain definitions.