← ClaudeAtlas

confluent-kafka-developerlisted

Kafka/Confluent developer skill for design, explanation, diagrams, planning, and review — designs event/topic/schema models, explains Kafka/Kafka Streams/ksqlDB/Flink concepts, draws architecture and data-flow diagrams, plans producer/consumer/streaming implementation work, and reviews Kafka client and Streams topology code. Searches official docs (docs.confluent.io, kafka.apache.org, developer.confluent.io) and community sources (Confluent Community Forum, Stack Overflow, relevant GitHub issues/discussions) before answering. Use when explaining a Kafka concept, designing an event-driven system, drawing a Kafka/Streams diagram, planning Kafka feature work, or reviewing Kafka producer/consumer/Streams/Connect code.
thititongumpun/skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill thititongumpun/skills
# Confluent / Kafka Developer For cluster provisioning, RBAC/networking, or ops — use `confluent-kafka-admin` instead. This skill is for designing, explaining, diagramming, planning, and reviewing Kafka *application* work. ## Research workflow Kafka/Confluent APIs, client configs, and best practices change across versions (KRaft, tiered storage, exactly-once semantics, new client configs) — don't answer from pretrained memory alone for anything version-specific. 1. **Official docs first**: start from [docs.confluent.io/llms.txt](https://docs.confluent.io/llms.txt) — Confluent's LLM-oriented doc index (~150 links organized by product/topic: Cloud, Platform, Flink, connectors, clients, security, CLI, etc.) — to find the right page fast, then fetch that specific page for exact details. Use [llms-full.txt](https://docs.confluent.io/llms-full.txt) for grounding on terminology/glossary questions, not as a substitute for the actual page. Also check [kafka.apache.org/documentation](https://kafka.apache.org/documentation/) for OSS-specific behavior, [developer.confluent.io](https://developer.confluent.io/) for patterns/courses/event-driven design guides, and the relevant client library docs (Java, Python, Go, .NET, librdkafka) — use context7 if available for exact client API surfaces. 2. **Community sources when docs don't settle it**: a specific error message, an edge case, or "does X actually behave like Y in practice" — search the [Conf