What problem does it solve? Designing streaming APIs that also work in hosting environments without streaming support (like Google App Engine Standard) requires careful naming conventions, backend lifecycle management, and client-side adapters. This Skill provides the guidelines and patterns to build Server-Side Streaming RPCs in KHI with transparent polling fallbacks. ## Core Features & Use Cases - API Naming Conventions: Defines Watch/Pull patterns for state observation and Action/ActionSync/CancelActionSync patterns for long-running jobs. - Backend Utilities: Covers StateObserver for atomic state snapshots and AsyncJobManager for background jobs with abandonment timeouts, TTL eviction, and superseded-job cancellation. - Frontend Interceptor: Explains the Connect interceptor that transparently adapts streaming calls into polling unary calls, including safe iterator extraction and automatic cancellation on client abort. - Use Case: When adding a new RPC like FilterTimeline to KHI, follow this Skill to define the protobuf pair, implement the backend job manager, and wire the legacy polling interceptor so the feature works in both streaming and non-streaming deployments. ## Quick Start Use the streaming-api skill to design a new streaming RPC with a polling fallback for the KHI backend and frontend.