agentleFS
imMamdouhaboammarimMamdouhaboammar/tiktok-growth-automation-mesh/grpc-microservices-guard/SKILL.md

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.

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
  1. Distinctive:

    All internal calls must strictly utilize gRPC over HTTP/2 with compiled Protocol Buffers.

    line 16
  2. Very specific:

    All schema changes must originate in the proto/ directory:

    line 18
  3. Distinctive:

    Every outgoing gRPC client call must set an explicit context deadline/timeout (default: 3000ms).

    line 24
  4. Very specific:

    Treat INVALID_ARGUMENT and ALREADY_EXISTS as terminal errors without retries.

    line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

gRPC Microservices Guard

Overview

Enforces communication protocols, protobuf schema synchronization, and boundary isolation rules defined in microservices_manifest.toon.

Core Invariants

  1. HTTP/JSON East-West Prohibition:
    • Internal inter-service traffic between api-gateway, task-scheduler-service, and growth-analytics-engine must NEVER use HTTP/JSON REST endpoints.
    • All internal calls must strictly utilize gRPC over HTTP/2 with compiled Protocol Buffers.
  2. 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.
  3. 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.
  4. 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_ARGUMENT and ALREADY_EXISTS as terminal errors without retries.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.