/develop

Document development patterns and architecture for the EventModeler application.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/sparkle-space/event-modeler --skill develop-sparkle-space
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /develop
Source: https://github.com/sparkle-space/event-modeler/tree/main/.claude/skills/develop
Command: npx skills add https://github.com/sparkle-space/event-modeler --skill develop-sparkle-space

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive guide to the core development patterns and architecture of the EventModeler application, enabling developers to understand and contribute to the project effectively.

Core Features & Use Cases

  • Architecture Overview: Details the technology stack (Elixir, Phoenix, LiveView, Commanded, PostgreSQL) and code organization.
  • Development Patterns: Explains key patterns like Commanded Aggregates, LiveView + SVG Canvas interaction, Two-Level Sync, and Event Enrichment.
  • Testing & Quality: Outlines testing strategies and code quality practices.
  • Use Case: A new developer joining the EventModeler project can use this Skill to quickly grasp the project's structure, understand how commands and events are handled, and learn how the interactive canvas is implemented.

Quick Start

Understand the core development patterns for the EventModeler application.

Frequently Asked Questions about /develop

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

FAQPage Schema
What development patterns are used for event sourcing in Elixir and Phoenix?

Event sourcing in Elixir and Phoenix uses Commanded Aggregates to handle commands and events, LiveView for interactive UI, PostgreSQL for data storage, and SVG for canvas rendering to structure the application architecture.

How does LiveView interact with an SVG canvas in a Phoenix application?

LiveView interacts with an SVG canvas using a Two-Level Sync pattern, enabling real-time collaborative canvas rendering for designing information systems directly within the Phoenix application without heavy JavaScript.

How do I organize code for a collaborative canvas application using Commanded?

Organize Commanded code by separating Aggregates for command handling and event enrichment, LiveView modules for SVG canvas interaction, and PostgreSQL projections for data storage, following structured development patterns.

What testing strategies are recommended for Elixir event sourcing applications?

Testing strategies for Elixir event sourcing applications focus on verifying Commanded Aggregate behaviors, validating event enrichment logic, and ensuring LiveView SVG canvas interactions function correctly through established code quality practices.

Does the EventModeler application use PostgreSQL for event storage?

Yes, the EventModeler application uses PostgreSQL for data storage, supporting the Commanded event sourcing framework to persist events and manage state for the collaborative canvas application built with Elixir.

What is the best way to implement event enrichment in an Elixir event sourcing system?

The best way to implement event enrichment in Elixir is using the Commanded framework's Aggregate patterns, which allow you to structure command processing and event generation cleanly within Phoenix and LiveView architectures.