skills.rest
signalbeam-io
signalbeam-ioOFFICIAL
Explore all skills by this author →
GitHub

add-event-handler

Scaffold WolverineFx event handlers with CancellationToken support and optional NATS publishing.

2|Updated Dec 9, 2025
Search Tags:#scaffold#dotnet#code-generation#nats#event-handler#wolverinefx#integration-events
One-click install
npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill add-event-handler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-event-handler
Source: https://github.com/signalbeam-io/signalbeam-edge/tree/main/.claude/skills/add-event-handler
Command: npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill add-event-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When building event-driven .NET applications, developers spend time boilerplating handlers for every domain or integration event. This skill generates a ready-to-use WolverineFx event handler scaffold that follows conventional patterns and reduces setup time.

Core Features & Use Cases

  • Event handler scaffold: creates a handler class in the appropriate Application.Events namespace with a strongly-typed @event parameter and CancellationToken support.
  • Integration event support: optionally scaffolds an integration event type for cross-service communication.
  • NATS publishing guidance: includes patterns for publishing events to NATS or similar messaging backplanes and shows how to wire the publisher in.
  • Use Case example: when a new DeviceRegisteredEvent is introduced, scaffold {EventName}Handler to react accordingly.

Quick Start

Provide the EventName and Service, and instruct the AI to scaffold a WolverineFx event handler and its optional integration event.

Frequently Asked Questions about add-event-handler

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

FAQPage Schema
How do I scaffold a WolverineFx event handler for a new domain event in .NET?▼

To scaffold a WolverineFx event handler, provide the EventName and Service to generate a conventional handler class in the Application.Events namespace with a strongly-typed @event parameter and CancellationToken support.

What is the conventional structure for WolverineFx event handlers in .NET applications?▼

The conventional WolverineFx event handler structure places handler classes in the Application.Events namespace, utilizing a strongly-typed @event parameter alongside CancellationToken support to ensure consistent reaction handling.

Can I scaffold integration events for cross-service communication with WolverineFx?▼

Yes, you can scaffold integration events for cross-service communication. The skill optionally generates an integration event type and provides NATS publishing patterns to wire the publisher into your WolverineFx handler.

How do I publish domain events to NATS using WolverineFx?▼

To publish domain events to NATS using WolverineFx, the scaffolded handler includes guidance for wiring in a publisher, allowing your .NET services to broadcast cross-service integration events over the messaging backplane.

Do I need to manually add CancellationToken support when scaffolding WolverineFx handlers?▼

No, manual CancellationToken setup is unnecessary. The scaffolded WolverineFx event handler automatically wires in CancellationToken support and the @event parameter, enforcing consistent handler structure without boilerplate.

Related Skills

Explore More Software Engineering Skills→
hiiamskyhiiamsky

domain-events-generator

Generate domain event records and handler scaffolding with outbox wiring.

Community
Advanced
PedroHBOPedroHBO
1

message-brokers

Implement RabbitMQ and Kafka messaging patterns for Python services.

Community
Advanced
zlzforeverzlzforever
1

bdd-dotnet

Write BDD-style .NET unit tests using EF Core InMemory databases and fluent builders.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

notification-handlers

Dispatch domain events via MediatR notification handlers after commit.

Community
Advanced