model-events-observers-workflows

What problem does it solve?

This Skill provides a robust pattern for managing complex application workflows triggered by model state changes, ensuring that side effects like event dispatching and job queuing are handled reliably and after database transactions are committed.

Core Features & Use Cases

• Explicit Domain Events: Encourages the use of specific, expressive events (e.g., fulfilled, cancelled) instead of generic ones (saved, updated).
• After-Commit Observers: Ensures that observers only react to events once database changes are successfully committed, preventing issues with rolled-back transactions.
• Decoupled Workflows: Separates model state persistence from side-effect orchestration, keeping models lean and workflows readable.
• Use Case: When a user's order status changes from 'pending' to 'shipped', this skill ensures that an audit log is created, an email notification is sent to the customer, and an integration with a shipping provider is triggered, all in a transactionally safe manner.

Quick Start

Use the model-events-observers-workflows skill to implement a pattern where a PurchaseOrder model's accepted event triggers a timeline event recording and dispatches a SyncToErp job.