Kafka Topic Designer

Designs and optimizes Apache Kafka topics and configurations

509 stars

Best use case

Kafka Topic Designer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Designs and optimizes Apache Kafka topics and configurations

Teams using Kafka Topic Designer should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/kafka-topic-designer/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/data-engineering-analytics/skills/kafka-topic-designer/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/kafka-topic-designer/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How Kafka Topic Designer Compares

Feature / AgentKafka Topic DesignerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Designs and optimizes Apache Kafka topics and configurations

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Kafka Topic Designer

## Overview

Designs and optimizes Apache Kafka topics and configurations. This skill provides expertise in topic architecture, partitioning strategies, and producer/consumer configuration for optimal streaming performance.

## Capabilities

- Topic naming convention design
- Partition strategy optimization
- Replication factor recommendations
- Retention policy configuration
- Compaction strategy design
- Schema registry integration
- Consumer group design
- Throughput capacity planning
- Security configuration (ACLs, encryption)

## Input Schema

```json
{
  "requirements": {
    "throughputMBps": "number",
    "messageSize": "number",
    "retentionDays": "number",
    "orderingRequirements": "string"
  },
  "existingTopics": ["object"],
  "clusterConfig": "object"
}
```

## Output Schema

```json
{
  "topicDesign": {
    "name": "string",
    "partitions": "number",
    "replicationFactor": "number",
    "configs": "object"
  },
  "schemaDefinition": "object",
  "producerConfig": "object",
  "consumerConfig": "object"
}
```

## Target Processes

- Streaming Pipeline
- ETL/ELT Pipeline (CDC)
- Feature Store Setup

## Usage Guidelines

1. Define throughput and latency requirements
2. Specify message size and retention needs
3. Document ordering requirements (per-partition, global)
4. Include existing topic configurations for consistency

## Best Practices

- Use consistent naming conventions across all topics
- Size partitions based on consumer parallelism needs
- Configure appropriate retention for compliance and replay scenarios
- Implement schema registry for schema evolution
- Set up proper ACLs for security

Related Skills