super-protobuf
Skill0 starsChanged 19 days agoMITView on GitHub
Protocol Buffers (proto3) design, buf.yaml/buf.gen.yaml, Connect and gRPC services, protovalidate, lint and breaking checks, schema evolution, mixed-version compatibility review, and defensive gRPC hardening. Use when writing or reviewing .proto files, setting up buf, generating Connect or gRPC code, adding protovalidate, catching breaking changes, or hardening an exposed gRPC surface — not for REST-only OpenAPI, GraphQL schemas, or offensive testing.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/commit-messages.mdcCursor rule
- .cursor/rules/git-workflow.mdcCursor rule
- .cursor/rules/manage-stack.mdcCursor rule
- .cursor/rules/no-worktrees.mdcCursor rule
- manage-stackSkill
- convert-as-skillSkill
- create-agentSkill
- create-agents-mdSkill
- create-commandSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- retrospectiveSkill
- super-architectureSkill
- super-cachingSkill
- super-elixirSkill
- super-nodejsSkill
- super-tech-blueprintSkill
- atomic-semantic-commitSkill
- code-reviewSkill
- create-bruno-collectionSkill
- create-documentationSkill
- create-ticketsSkill
- ready-specSkill
- write-adrSkill
- write-changelogSkill
- write-mr-descriptionSkill
- write-planSkill
- write-postmortemSkill
- write-runbookSkill
- noslopSkill
- output-saversSkill
- safe-refactorSkill
- tddSkill
- verifySkill
- get-movingSkill
- later-listSkill
- standupSkill
- challenge-meSkill
- codebase-learnerSkill
- researchSkill
- second-opinionSkill
- traceSkill
- color-kitSkill
- design-system-kitSkill
- diagramSkill
- infographicSkill
- product-polish-workflowSkill
- prototype-wireframeSkill
- ui-ux-kitSkill
- evidenceSkill
- find-skillsSkill
- handoffSkill
- rumblingSkill
- use-levistackSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Do this first; do not announce it.
- Distinctive: line 70
Review-compat: when consumers, storage, or mixed versions exist.
- Very specific: line 72
Check the Makefile or package.json first—many repos wrap these as make lint / make generate.
- Distinctive: line 76
Keep this router lean. Do not paste language samples or extra checklists here.
- Very specific: line 78
Language track: add references/tech/<lang>.md (one screen), one row in references/tech/README.md, and one row in the Step 0 table.
- Very specific: line 79
Template: add a file under templates/ or assets/ and mention its basename in templates/README.md.
- Very specific: line 80
Core topic: add references/core/<topic>.md and one table row here.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Super protobuf
One router for proto3 schemas, the buf toolchain, Connect/gRPC services, and compatibility review. Language-agnostic core; language tracks are optional and short.
Merged scope: formerly protobuf. Index: references/README.md. Research: research-synthesis.md.
Principles
- Match the repo first. Copy existing package layout, field order, validation, and comments. If none exist, use this skill's defaults.
- Buf is the default toolchain.
buf format -w && buf lint, thenbuf breaking --against '.git#branch=main'when the schema already shipped. EasyP is a buf-compatible alternative, not a second source of truth. - Protovalidate on production fields. The
.protofile is the contract for structure and constraints. - Evolve additively. New fields, enum values, and RPCs stay in
v1. Breaking changes get a new package version. Never reuse field or enum numbers. - Treat gRPC as an API. Authz on every method, including "internal" services that just became reachable. Do not leak
.protofiles or descriptors. Do not run or document attacks.
Step 0: detect the job
Do this first; do not announce it. If the request already names a mode, go there.
| If the user is doing this | Mode | Load |
| New messages, RPCs, package layout, AIP-style resources | design | modes/design.md, design.md |
buf.yaml / buf.gen.yaml, generate stubs, Connect vs gRPC | generate | modes/generate.md, buf-workflow.md |
| Review a proto diff, mixed-version deploys, wire vs JSON vs storage | review-compat | modes/review-compat.md, compatibility.md |
buf lint / buf breaking, naming, EasyP as alternative | lint-breaking | modes/lint-breaking.md, style.md |
| Auth on gRPC, reflection, grpc-web, leaked schemas | harden | security.md |
| Go plugins, opaque API | language: Go | go.md |
| Elixir / protobuf-elixir | language: Elixir | elixir.md |
| C# / grpc-dotnet | language: C# | csharp.md |
| Connect vs gRPC choice | rpc stack | connect-vs-grpc.md |
Stack index: references/tech/README.md. Depth: evolution.md, protovalidate.md, review-checklist.md, quick-reference.md, troubleshooting.md, migration.md, protoc-toolchain.md.
Default pipeline
- Detect the job (table above).
- Design the messages and RPCs. Copy templates/ or assets/proto/example/v1/.
- Generate with the project's
buf.gen.yaml(templates in assets/). - Verify:
buf format -w && buf lint. If the schema shipped,buf breaking --against '.git#branch=main'. - Review-compat when consumers, storage, or mixed versions exist.
Check the Makefile or package.json first—many repos wrap these as make lint / make generate.
Contribute
Keep this router lean. Do not paste language samples or extra checklists here.
- Language track: add
references/tech/<lang>.md(one screen), one row inreferences/tech/README.md, and one row in the Step 0 table. - Template: add a file under
templates/orassets/and mention its basename in templates/README.md. - Core topic: add
references/core/<topic>.mdand one table row here. Prefer extending an existing file.
Old skill name
| Old | Use |
protobuf | This skill (super-protobuf) |
Related skills
super-elixir: the service is Elixir.super-nodejs: the service is Node and uses Connect or gRPC.super-architecture: decide service boundaries before you design the schema.verify: show buf lint and breaking output before you claim compatibility.create-bruno-collection: add runnable gRPC examples as a Bruno collection.
Done when
- The matching mode ran; only needed references were opened.
buf format -w && buf lint(or the project's wrap) succeeded; breaking check ran when the schema already shipped.- Production fields have protovalidate constraints; reserved numbers cover removals.
- gRPC exposure was treated as an API (authz, no schema leak) when that was in scope.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.