Kafka Streaming taste — ChatGPT prompt: what it does, how to install
Kafka Streaming taste is a prompt for ChatGPT, Claude.ai, and Claude Code that defines Kafka streaming architecture and design rules.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Kafka Streaming taste does
The prompt sets engineering rules for Apache Kafka development, covering domain-based topic naming like orders.order-placed.v1, schema registry enforcement with Avro or Protobuf, and partition key selection based on entity identifiers. Producer configurations require enabled idempotency, acks=all, and min.insync.replicas=2 with a replication factor of 3 for critical business paths.
Instructions dictate at-least-once delivery semantics, dead-letter topic routing for persistent failures, offset commits following side-effect completion, and transactional outbox usage for atomic database writes. Topic topologies, partitions, retention policies, and ACLs are managed as code reviewed via pull requests, with automatic topic creation disabled in production environments.
Integration tests run against real brokers inside containers, while cluster security relies on TLS, client authentication, and service-specific ACLs. Events are structured in the past tense as factual occurrences rather than imperative commands.
To install in Claude Code, place the prompt file at .claude/commands/prompts.csv.md.
What it helps with
- design Kafka topics and partitions
- configure producer idempotency and delivery guarantees
- manage Avro and Protobuf schemas in a registry
- handle transient failures and dead-letter topics
- implement transactional outbox and stateful joins
Example prompts for the agent
- Apply Kafka Streaming taste standards to design domain topics and partitions
- Configure the Kafka producer with idempotency and acks settings according to Kafka Streaming taste
- Set up error handling and dead-letter queue routing for Kafka consumers following Kafka Streaming taste
How to install Kafka Streaming taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Kafka Streaming taste
How to install Kafka Streaming taste in Claude Code?
Save the prompt file to your repository at .claude/commands/prompts.csv.md.
What does Kafka Streaming taste do?
It provides architecture guidelines and design standards for event-driven systems using Apache Kafka, covering topic naming, serialization, delivery guarantees, and infrastructure as code.
What producer settings are required for critical data?
Producers must run with acks=all, idempotency enabled, and min.insync.replicas=2 on a replication factor of 3.
Source text
prompts.csv · CC0-1.0
# Kafka Streaming taste of a pragmatic event platform engineer - Name topics by domain and event, such as `orders.order-placed.v1`, and put the schema version in the name only when a breaking change forces a new topic. Confidence: 0.85 - Register every topic schema in a schema registry (Avro or Protobuf) with backward compatibility enforced; never publish raw untyped JSON to shared topics. Confidence: 0.90 - Choose the partition key from the entity whose ordering matters (order id, account id), and never rely on ordering across partitions. Confidence: 0.95 - Start with enough partitions for expected peak consumer parallelism plus headroom, because increasing partitions later breaks key-to-partition mapping. Confidence: 0.80 - Run producers with `acks=all`, idempotence enabled and `min.insync.replicas=2` on a replication factor of 3 for anything business-critical. Confidence: 0.90 - Treat delivery as at-least-once and make every consumer idempotent with a dedupe key or upsert, instead of chasing end-to-end exactly-once. Confidence: 0.90 - Commit offsets only after the side effect has succeeded; disable auto-commit for consumers that write to databases or call APIs. Confidence: 0.90 - Send messages that fail repeatedly to a dead-letter topic with the original headers, error and attempt count, and alert on its growth. Confidence: 0.85 - Retry transient failures with bounded backoff inside the consumer before dead-lettering; never block a partition forever on one poison message. Confidence: 0.85 - Keep events as facts in past tense that describe what happened, not commands telling another service what to do. Confidence: 0.80 - Keep payloads small and self-contained enough to process without a synchronous call back to the producer, but put large blobs in object storage and send a reference. Confidence: 0.75 - Use the transactional outbox pattern to publish events atomically with database writes instead of dual writes. Confidence: 0.90 - Use log compaction for topics that represent the latest state per key, and time-based retention for pure event streams. Confidence: 0.85 - Monitor consumer lag per group and partition as the primary health signal, alerting on sustained growth rather than single spikes. Confidence: 0.90 - Put a correlation id and the producing service name in message headers so traces can follow an event across services. Confidence: 0.80 - Give every consumer group a stable, descriptive id tied to the service, and never share one group between unrelated applications. Confidence: 0.85 - Reach for Kafka Streams or Flink only when you need stateful joins or windowing; a plain consumer is simpler for stateless transforms. Confidence: 0.75 - Manage topics, partitions, retention and ACLs as code reviewed in pull requests, and disable automatic topic creation in production. Confidence: 0.90 - Lock down clusters with TLS, authenticated clients and per-service ACLs that grant only the topics each service needs. Confidence: 0.85 - Test consumers against a real broker in containers for integration tests, and keep unit tests on pure handler functions. Confidence: 0.80 - Document each topic's owner, schema, key, retention and consumers in a catalog that lives next to the topic definitions. Confidence: 0.70
© f · CC0-1.0 · f/prompts.chat