grpc-microservices-guard
Skill0 starsChanged 47 days agoMITView on GitHub
Enforce gRPC communication standards, protobuf schema evolution, and East-West isolation rules across the microservices mesh.
In this repository22 other files it gives its agents.
- async-python-patternsSkill
- bun-runtimeSkill
- contract-firstSkill
- distributed-tracingSkill
- docker-patternsSkill
- fastapi-patternsSkill
- golang-concurrencySkill
- golang-error-handlingSkill
- golang-grpcSkill
- golang-patternsSkill
- golang-performanceSkill
- golang-testingSkill
- grpc-microservices-guardSkill
- microservices-patternsSkill
- openapi-spec-generationSkill
- redis-patternsSkill
- social-media-automation-orchestratorSkill
- tdd-workflowSkill
- verification-loopSkill
- x-apiSkill
- tiktok-growth-automation-meshSkill
- social-media-automation-orchestratorSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
All internal calls must strictly utilize gRPC over HTTP/2 with compiled Protocol Buffers.
- Very specific: line 18
All schema changes must originate in the proto/ directory:
- Distinctive: line 24
Every outgoing gRPC client call must set an explicit context deadline/timeout (default: 3000ms).
- Very specific: line 29
Treat INVALID_ARGUMENT and ALREADY_EXISTS as terminal errors without retries.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
gRPC Microservices Guard
Overview
Enforces communication protocols, protobuf schema synchronization, and boundary isolation rules defined in microservices_manifest.toon.
Core Invariants
- HTTP/JSON East-West Prohibition:
- Internal inter-service traffic between
api-gateway,task-scheduler-service, andgrowth-analytics-enginemust NEVER use HTTP/JSON REST endpoints. - All internal calls must strictly utilize gRPC over HTTP/2 with compiled Protocol Buffers.
- Internal inter-service traffic between
- Contract-First Protocol Buffers:
- All schema changes must originate in the
proto/directory:proto/booster/: Scheduler and task dispatch contracts.proto/analytics/: AI scoring and trend telemetry contracts.
- Generated code must be compiled for Bun/TypeScript, Go, and Python respectively before building services.
- Backward compatibility rules: Never change existing field numbers or rename serialized proto field IDs. Always use additive field changes with optional or default semantics.
- All schema changes must originate in the
- Deadlines & Context Propagation:
- Every outgoing gRPC client call must set an explicit context deadline/timeout (default: 3000ms).
- Distributed tracing context (W3C TraceContext
traceparent) must be propagated in gRPC metadata across service hops.
- Resilience & Circuit Breaking:
- Connection pools must handle gRPC channel reconnections gracefully.
- Implement client-side retries only for idempotent methods (
GET/read semantics) and transient status codes (UNAVAILABLE,RESOURCE_EXHAUSTED). - Treat
INVALID_ARGUMENTandALREADY_EXISTSas terminal errors without retries.
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.

