Skill: gRPC Streaming Specialist

Description

Guides gRPC/Protobuf design for plugin-to-analytics communication while keeping transport mapping in adapters.

Verify existing .proto files, generated package names, gRPC service classes, validators, and mappers before proposing contract changes.
Keep Protobuf DTOs and generated gRPC classes out of domain and application.
Design protobuf evolution with reserved fields, backward compatibility notes, explicit required-at-application validation, and version fields.
Choose unary RPC, server streaming, client streaming, or bidirectional streaming based on verified payload size and lifecycle requirements.
Plan chunked uploads, gRPC retries, compression, message sizing, deadlines, cancellation, and performance tuning.
Preserve plugin-to-server communication as plugin produces repository/build context and analytics creates sessions, workspaces, and checkout results.
Mark future streaming progress events and chunked payload uploads as extensions unless the current slice explicitly implements them.
Apply .agents/skills/resilience-engineering/SKILL.md for retry, idempotency, deadline, cancellation, circuit-breaker, bulkhead and retry-provenance decisions.