Event-Driven Messaging

Event-Driven Messaging is an AI Engineering skill for Claude Code, published by rrezartprebreza in spring-boot-skills.

247 stars39 forkson rrezartprebreza/spring-boot-skillsAdded 2026/09/02+7% in starsRepository updated 2026/08/14

ai-coding-agentclaudeclaude-aiclaude-codeclaude-pluginclaude-skillclaude-skillscodexcodex-skillsdeveloper-toolsjavamcpspring-aispring-boot

Install in seconds

Install Event-Driven Messaging

Copy Event-Driven Messaging into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-3/event-driven-messaging ~/.claude/skills/event-driven-messaging

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/rrezartprebreza/spring-boot-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/spring-boot-3/event-driven-messaging/SKILL.md in rrezartprebreza/spring-boot-skills
Installs to: ~/.claude/skills/event-driven-messaging
Collection: One of 24 skills cataloged from this repository
Category: AI Engineering — 2631 skills

What Event-Driven Messaging does

Event-Driven Messaging guides Kafka, RabbitMQ, Pulsar, and JMS producers and consumers in Spring Boot 3. It covers event contracts, idempotency, retries, dead-letter handling, ordering, and outbox delivery.

Event-Driven Messaging is cataloged under AI Engineering on DirSkills. Event-Driven Messaging comes from a repository tagged ai-coding-agent, claude, claude-ai, claude-code and claude-plugin.

Documentation

README

Excerpt

Event-Driven Messaging

Design for at-least-once delivery unless the complete system proves stronger semantics.

Event contract

Use an immutable event envelope with eventId, eventType, occurredAt, schemaVersion, and payload.
Treat published schemas as APIs. Add fields compatibly and never silently change meaning.
Put correlation and causation IDs in headers or the envelope.
Do not publish JPA entities or framework-specific serialization shapes.

Producer rules

Publish only after the originating state change is durable.
Use a transactional outbox when database state and broker publication must agree.
Use deterministic partition keys when per-aggregate ordering matters.
Configure delivery timeout and acknowledgements explicitly.

Consumer rules

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Event-Driven Messaging

What else does rrezartprebreza publish alongside Event-Driven Messaging?
Event-Driven Messaging is one of 24 skills that DirSkills catalogs from rrezartprebreza/spring-boot-skills, the repository it ships in. Its siblings there include AI Observability, API Versioning and Container Native Deployment. Each one is a separate skill with its own page in this directory, installs the same way Event-Driven Messaging does, and is maintained by rrezartprebreza in that same repository. The rest of the collection is listed on the rrezartprebreza/spring-boot-skills page.
How does Event-Driven Messaging compare to other AI Engineering skills?
Event-Driven Messaging ranks #2335 by stars among the 2631 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Event-Driven Messaging against them. Open each page to compare what they document and how they install.