event-driven plugins

by Jeremy Longshore

Implement event-driven APIs with message queues and event streaming

by Jeremy Longshore

Implement event-driven APIs with message queues and event streaming

by Jeremy Longshore

Implement event-driven APIs with message queues and event streaming

by Matt Corbett

API engineering specialist team — agents (api-design-architect, api-implementation-engineer, api-security-engineer, api-testing-engineer, api-platform-engineer) for the full lifecycle of an API you produce: paradigm choice (REST/GraphQL/gRPC/webhooks/AsyncAPI), contract-first design (OpenAPI 3.1/3.2, AsyncAPI 3.0, Arazzo), versioning & deprecation; the build craft (RFC 9457 Problem Details, cursor pagination, Idempotency-Key, ETag concurrency, HTTP semantics, 202+polling, RateLimit headers); security (OWASP API Security Top 10 2023 — BOLA/BOPLA/BFLA, token/scope validation, consumption limits, SSRF); and testing & operations (contract tests, Spectral lint in CI, Prism/Postman mocks, k6 load, gateway design, dev portal + SDK codegen, sunset rollout). Knowledge bank with Mermaid decision trees + a dated 2026 capability map, best-practices, templates, commands, an advisory hook. Security verdicts escalate to ravenclaude-core/security-reviewer. Requires ravenclaude-core@>=0.7.0.

by Matt Corbett

Data-streaming-engineering team — agents (streaming-architect, kafka-pipeline-engineer, stream-processing-engineer) for REAL-TIME data: streaming-vs-batch decision and topology, event streaming + CDC (Kafka/Pulsar/Kinesis, topics/partitioning, schema registry + evolution, the outbox/Debezium CDC pattern), delivery semantics (at-least-once vs exactly-once, idempotency, transactional outbox), and stream processing (Flink/Kafka-Streams: event-time vs processing-time, windowing, watermarks, state, joins, backpressure). skills, a decision-tree knowledge bank (streaming-vs-batch + delivery-semantics trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Distinct from data-platform (batch ELT) and microsoft-fabric (RTI/Eventstream). Seams: batch ELT -> data-platform, AsyncAPI contracts -> api-engineering, Fabric RTI -> microsoft-fabric, app-side messaging -> backend-engineering. Requires ravenclaude-core@>=0.7.0.

by Matt Corbett

Serverless engineering team — agents for building on serverless the provider-neutral way. serverless-architect owns the design side: event-driven decomposition, FaaS-vs-containers-vs-managed-services and when serverless is the WRONG choice, sync/async, orchestration-vs-choreography, event contracts, the dual-write/outbox problem, and serverless-friendly storage. serverless-runtime-and-ops-engineer owns the runtime side: cold starts, concurrency & throttling, idempotency & exactly-once-effect, DLQs & poison messages, retries, per-invocation cost & the scale crossover, tracing in ephemeral runtimes, and local emulation. skills, a knowledge bank (a Mermaid decision tree + a dated 2026 patterns reference), templates. Provider-neutral PATTERNS only — distinct from aws-cloud/gcp-cloud/azure-cloud (provider IaC/specifics), data-streaming-engineering (Kafka/Kinesis), devops-cicd (deploy pipeline), backend-engineering (the serverful alternative), observability-sre (SLOs). Requires ravenclaude-core@>=0.7.0.