메뉴
Example Data Skill - Guide for adding example data to Command, Event, and Information elements in prooph board. Covers YAML examples with concrete values and documenting state changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Animal Shelter Academy - A BusinessSeriesModeling experiment where stories become training grounds for Event Modeling. Follow Caramelo's journey, interview stakeholders, uncover the operational reality behind the narrative, and learn that the story people remember and the processes they live are often two sides of the same truth.
Add a complete schema to commands, events, or information elements based on example data or event modeling context.
Event Modeling Skill - Core guidelines for creating Event Models on prooph board. Covers event-first modeling strategy, command eligibility tests, element types, lane and slice structure, anti-patterns, and self-validation. Use this skill to understand the rules of Event Modeling on prooph board.
Prooph Board Navigation Skill - Parses deeplinks, retrieves chapter data via MCP, focuses on referenced elements or slices, and generates deeplinks for precise user navigation.
Generate hand-drawn style SVG wireframes with sketchy aesthetics. Includes validation rules to prevent layout overlap and ensure proper element spacing.
Implement automation slices (Event to Command) using Axon Framework 5, Vertical Slice Architecture, and Event Modeling patterns. An automation is: an Event Handler that reacts to an event by dispatching a command via CommandDispatcher. Automations can be stateless (direct event-to-command mapping) or with a private read model (to look up data needed for command construction). Use when: (1) implementing a new automation / event-to-command reactor in an AF5 project, (2) migrating/porting an automation from Axon Framework 4 (Java or Kotlin) to AF5, (3) user provides a specification, Event Modeling artifact, or natural language description of an event-to-command reaction and asks to implement it, (4) user says "implement", "create", "add", "migrate", "port" an automation, event handler, reactor, or event-to-command flow in an Axon Framework 5 / Vertical Slice Architecture project. Understands AF4 @EventHandler/@ProcessingGroup input as one possible source format.
| name | example-data |
| description | Example Data Skill - Guide for adding example data to Command, Event, and Information elements in prooph board. Covers YAML examples with concrete values and documenting state changes. |
This document describes how to add concrete example data to Command, Event, and Information elements in prooph board using YAML code blocks.
Example data in element descriptions helps:
✅ Good:
employee: Anna
location: loc-abc
startTime: 9am
❌ Avoid:
employeeId: string|format:uuid
locationId: string|format:uuid
startTime: string|format:time
Use schema/type definitions in element details (f.e. cody-schema), not in descriptions.
Include only the fields relevant to understand this specific process step. Don't dump every possible field.
Commands represent business actions that change persistent system state. Show the data the command carries as input.
trackingId: uuid
employee: uuid
location: uuid
day: 2026-03-05
startTime: 09:00
breaks:
-
startTime: 13:00
endTime: 13:30
-
startTime: 15:00
endTime: 15:15
endTime: 18:00
notes: Worked late on project documentation
Use when: The command has significant data that needs explanation.
trackingId: track1
Use when: The command only needs a reference ID and the context makes everything else clear.
Events represent business facts that became true. Show the state change the event carries.
trackingId: track1
# ...
breaks:
-
startTime: 1pm
endTime: now()|time()
The # ... indicates that other data from the state remains unchanged. Use now()|time() to show dynamic values computed at runtime.
trackingId: track1
Use when: The event only carries an entity reference and the fact itself is clear from the event name.
Information represents data read from the system. Show a snapshot of available information.
trackingId: track1
employee: Anna
location: loc-abc
day: 2026-03-05
startTime: 9am
breaks:
-
startTime: 1pm
endTime: 1:30pm
endTime: 6pm
overtime: 0
Use when: Showing the full state after multiple events helps understand the process.
trackingId: track1
employee: Anna
location: loc-abc
day: 2026-03-05
startTime: 9am
Use when: Only certain fields are relevant to this step or the information represents a query result with limited fields.
If the information element name is self-explanatory and the technical details in element details provide full specification, no example data may be needed.
```markdown
**Before**: Employee is not clocked in
**After**: Time tracking session started at 09:00 AM
This pattern makes state transitions explicit for business understanding.
When adding example data to an element, check the width of the slice the element belongs to. If the width is less than 320, use the resize_slice tool to set the slice width to 320 before or after updating the element description. Do it only once per slice.
```markdown
❌ Bad:
The command handler validates the schema and if valid, records an event to the event store which triggers projections to update the read model.
✅ Better:
System records the clock-in time and starts tracking work hours.
❌ Bad:
trackingId: track1
✅ Better:
trackingId: track1
employee: Anna
location: loc-abc
Provide enough context so readers understand what the data represents.
❌ Bad:
{
"timeTrackingId": "string|format:uuid",
"employeeId": "string|format:uuid"
}
✅ Better:
trackingId: track1
employee: Anna
Descriptions use example data; details use schema definitions.