integration-event-creator

Creates Kotlin event classes, JSON schemas, tests, docs, and listener stubs.

Updated May 15, 2026
One-click install
npx skills add https://github.com/avgarcia/runcriticon --skill integration-event-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-event-creator
Source: https://github.com/avgarcia/runcriticon/tree/main/.claude/skills/integration-event-creator
Command: npx skills add https://github.com/avgarcia/runcriticon --skill integration-event-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent integration event implementations by coordinating the creation of all required artifacts for public backend events across a modular architecture.

Core Features & Use Cases

  • Event Artifact Generation: Creates Kotlin integration event classes, versioned JSON Schemas, contract tests, module documentation updates, and consumer listener stubs.
  • Architecture Alignment: Applies established event-driven patterns such as required context fields, schema versioning, and idempotent event consumption.
  • Use Case: When a running club platform introduces a new domain fact like a published training plan or updated athlete record, use this Skill to generate the complete event contract workflow.

Quick Start

Ask the integration event creator skill to create a new public integration event for a backend module and include all required artifacts.

Frequently Asked Questions about integration-event-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate integration events and JSON schemas for a Kotlin backend module?

You can generate Kotlin integration event classes alongside versioned JSON schemas by applying an event-driven architecture pattern that coordinates all required public event artifacts for modular backend development.

What is the best way to create consistent contract tests for event-driven architecture in Spring Modulith?

Creating consistent contract tests for Spring Modulith involves generating versioned contracts and validation tests simultaneously with the event classes to ensure domain facts are published reliably across modules.

How do I scaffold idempotent listeners for domain events in Kotlin?

Scaffolding idempotent listeners requires generating consumer listener stubs that safely handle duplicate domain event deliveries, applying established event-driven architecture patterns for modular backends.

Can I use this approach to publish versioned contracts for modular monoliths?

Yes, applying this approach to modular monoliths allows you to create versioned contracts and context fields that ensure domain facts are safely consumed by other modules within the architecture.

Why do my backend integration events lack consistency across different modules?

Integration events lack consistency when required artifacts like JSON schemas, contract tests, and documentation are generated separately, rather than being coordinated through a unified event contract workflow.