One-click install
npx skills add https://github.com/howarddierking/mermaid-event-model --skill add-slices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-slices
Source: https://github.com/howarddierking/mermaid-event-model/tree/main/skills/add-slices
Command: npx skills add https://github.com/howarddierking/mermaid-event-model --skill add-slices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes stale or missing vertical slices in an Event Model DSL by regenerating slice declarations directly from the current edge graph inside the Mermaid eventModel block.

Core Features & Use Cases

  • Idempotent slice regeneration: Strips existing slice blocks first, then rewrites fresh slices so re-running never accumulates duplicates.
  • Canonical Event Modeling patterns: Detects and groups edges into the four recognized slice patterns, including the Automation Pattern where Event(s) → View → Automation → Command → Event(s) remains a single slice.
  • Edge classification + verification: Classifies edges by (source-kind, target-kind), surfaces unclassified edges, and validates that every bare edge ends up in exactly one slice.

Quick Start

Analyze and rewrite the slices in your Event Model DSL file by running the skill with the path to your markdown DSL file.

Frequently Asked Questions about add-slices

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

FAQPage Schema
How do I regenerate stale slices in an Event Model DSL from a Mermaid graph?

You can regenerate stale slices in an Event Model DSL by parsing the edges inside the Mermaid eventModel block, classifying source and target element kinds, and rewriting slices deterministically. Existing slice blocks are stripped first to prevent duplicate accumulation.

What are the recognized slice patterns in Event Modeling automation?

Event Modeling automation recognizes four canonical slice patterns. The Automation Pattern specifically groups an Event-to-View-to-Automation-to-Command-to-Event sequence into a single slice, ensuring complex workflows remain cohesive during generation.

How do I update existing blueprint-style Event Models without losing non-slice content?

To update blueprint-style Event Models without losing content, apply idempotent slice regeneration. The process removes and replaces stale slice blocks while preserving all non-slice content outside the fenced Mermaid eventModel block.

Can I verify that every bare edge in an Event Model graph is accounted for?

Yes, you can verify bare edges by classifying edge source and target kinds, surfacing unclassified edges, and validating that every bare edge ends up in exactly one generated slice for complete graph coverage.

Why do my Event Model slices accumulate duplicates when I rerun generation?

Slices accumulate duplicates when generation lacks idempotency. An idempotent rewrite approach strips existing slice blocks first before emitting fresh Pattern 1/2/3/4 slices with consistent naming, ensuring re-running never adds duplicates.