/514-frameworks-micronaut-kafka
Use when you need Kafka messaging in Micronaut — including @KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, and error handling. This should trigger for requests
Claude Code
$ npx -y skills add jabrena/plinth --skill 514-frameworks-micronaut-kafka --agent claude-code
Codex
$ npx skills add jabrena/plinth --skill 514-frameworks-micronaut-kafka -a codex -y
Cursor
$ npx skills add jabrena/plinth --skill 514-frameworks-micronaut-kafka -a cursor -y
Gemini CLI
$ npx skills add jabrena/plinth --skill 514-frameworks-micronaut-kafka -a gemini-cli -y
GitHub Copilot
$ npx skills add jabrena/plinth --skill 514-frameworks-micronaut-kafka -a github-copilot -y
OpenCode
$ npx skills add jabrena/plinth --skill 514-frameworks-micronaut-kafka -a opencode -y
Windsurf
$ npx skills add jabrena/plinth --skill 514-frameworks-micronaut-kafka -a windsurf -y
SKILL.md
514-frameworks-micronaut-kafka.SKILL.mdname: 514-frameworks-micronaut-kafka
description: Use when you need Kafka messaging in Micronaut — including @KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, and error handling. This should trigger for requests such as Add Kafka in Micronaut; Review Micronaut Kafka listeners; Improve retry and failure handling for Micronaut Kafka; Configure Micronaut Kafka clients listeners or SerDes; Add Micronaut Kafka retry or dead-letter handling. Part of Plinth Toolkit
license: Apache-2.0
metadata:
author: Juan Antonio Breña Moral
version: 0.19.0
Micronaut — Kafka messaging
Apply Micronaut Kafka guidance with concrete examples for design, implementation, and error handling.
Constraints
Compile before messaging refactors; verify after changes.
- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change
- **SAFETY**: If compilation fails, stop immediately
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements
- **BEFORE APPLYING**: Read the reference for detailed rules and examples
When to use this skill
- Add Kafka in Micronaut
- Review Micronaut Kafka consumers/producers
- Improve retries, dead-letter handling, or idempotency in Micronaut Kafka
- Configure Micronaut Kafka clients listeners or SerDes
- Add Micronaut Kafka retry or dead-letter handling
Workflow
1. **Read reference and assess project context**
Read `references/514-frameworks-micronaut-kafka.md` and inspect current messaging setup before proposing changes.
2. **Gather scope and decide target improvements**
Identify delivery guarantees and resilience requirements to define safe improvements.
3. **Apply framework-aligned changes**
Implement/refactor clients, listeners, and failure strategies in Micronaut Kafka.
4. **Run verification and report results**
Execute build/tests and summarize what changed, what was verified, and follow-up actions.
Reference
For detailed guidance, examples, and constraints, see [references/514-frameworks-micronaut-kafka.md](references/514-frameworks-micronaut-kafka.md).
Read more
name: 514-frameworks-micronaut-kafka description: Use when you need Kafka messaging in Micronaut — including @KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, and error handling. This should trigger for requests such as Add Kafka in Micronaut; Review Micronaut Kafka listeners; Improve retry and failure handling for Micronaut Kafka; Configure Micronaut Kafka clients listeners or SerDes; Add Micronaut Kafka retry or dead-letter handling. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0
Micronaut — Kafka messaging
Apply Micronaut Kafka guidance with concrete examples for design, implementation, and error handling.
Constraints
Compile before messaging refactors; verify after changes.
- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change
- **SAFETY**: If compilation fails, stop immediately
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements
- **BEFORE APPLYING**: Read the reference for detailed rules and examples
When to use this skill
- Add Kafka in Micronaut
- Review Micronaut Kafka consumers/producers
- Improve retries, dead-letter handling, or idempotency in Micronaut Kafka
- Configure Micronaut Kafka clients listeners or SerDes
- Add Micronaut Kafka retry or dead-letter handling
Workflow
1. **Read reference and assess project context**
Read `references/514-frameworks-micronaut-kafka.md` and inspect current messaging setup before proposing changes.
2. **Gather scope and decide target improvements**
Identify delivery guarantees and resilience requirements to define safe improvements.
3. **Apply framework-aligned changes**
Implement/refactor clients, listeners, and failure strategies in Micronaut Kafka.
4. **Run verification and report results**
Execute build/tests and summarize what changed, what was verified, and follow-up actions.
Reference
For detailed guidance, examples, and constraints, see [references/514-frameworks-micronaut-kafka.md](references/514-frameworks-micronaut-kafka.md).
Other skills on plinth.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about 514-frameworks-micronaut-kafka.
- Which coding agents can use 514-frameworks-micronaut-kafka?
- 514-frameworks-micronaut-kafka installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

