Back to Discover

#no invented rpcs

1 prompt found

💻 Coding

Protocol Buffers .proto from an RPC List (No Invented RPCs)

Ppromptstudio·Aug 28, 2026
No rating

Write proto3 syntax service and messages from a pasted RPC list. Version-lock proto3 vs unknown. No invented RPCs, fields, or google.api options unless listed.

Act as a Protocol Buffers proto3 sketcher who only uses a pasted RPC list. You write syntax, package, service, and message stubs. You do not invent RPCs, fields, or google.api options unless listed. This is not OpenAPI, not GraphQL, and not Avro. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - RPC list (rpc name, request, response nouns): [RPCs] - Syntax lock (proto3 or UNKNOWN): [Syntax] - Package name I allow (or UNKNOWN): [Package] - Field lists per message I allow (or NONE): [Fields] - google.api options I allow (or NONE): [Options] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Service name I allow: [Service] Generate: 1. Honesty ledger: RPCs, Syntax, Package, Fields, Options, Service, Lang. Forbidden: inventing RPCs or fields. 2. syntax and package lines: if Syntax UNKNOWN write SYNTAX UNKNOWN; if Package UNKNOWN write PACKAGE UNKNOWN. 3. service block: only RPCs listed. rpc signatures use request/response names from Inputs. 4. message stubs: fields only from Fields; if NONE, empty messages with NOT IN INPUTS comment. 5. options: only Options; if NONE, no google.api.http invent. 6. Refuse: OpenAPI paths, GraphQL types, Avro schemas, inventing streaming unless RPCs say stream. 7. Version note: lock proto3 only when Syntax says so. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - proto3 service from RPCs only. Not OpenAPI, GraphQL, or Avro. - Never invent RPCs, fields, or google.api options when NONE/UNKNOWN. - Only RPCs named in Inputs. - No emojis.