ワンクリックでManusで任意のスキルを実行

em-proophboard-backup

スター3

フォーク1

更新日2026年3月9日 23:18

Backup proophboard Event Modeling workspace to local JSON files. Downloads all chapters (with lanes, slices, elements) into .proophboard/chapters/ and records backup metadata. Use when: (1) user says 'backup', 'sync', 'download', 'snapshot' in context of proophboard or event model, (2) user wants to save the current board state to git, (3) user says 'em-proophboard-backup' or '/em-proophboard-backup'.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

MateuszNaKodach

MateuszNaKodach/HeroesOfDomainDrivenDesign.EventSourcing.DCB.Kotlin.Axon5.Spring

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

proophboard Backup

Download the full proophboard workspace into local .proophboard/backup JSON files.

Procedure

Run the backup script:

node .proophboard/scripts/backup.mjs

The script reads PROOPHBOARD_API_KEY from .proophboard/.env.local (preferred, gitignored) or .proophboard/.env, falling back to the environment variable.

If the key is missing and .proophboard/.env.local does not exist, ask the user to provide it, then write it to .proophboard/.env.local:

PROOPHBOARD_API_KEY=pb_xxxx

Report the script's stdout output to the user.

このリポジトリの他の Skills

同じリポジトリ

code-review

MateuszNaKodach/HeroesOfDomainDrivenDesign.EventSourcing.DCB.Kotlin.Axon5.Spring

Project-specific review checklist for this repository (DDD + Event Sourcing + Axon Framework 5 invariants). Use when: (1) reviewing code changes, a diff, or a pull request in this repository, (2) user says 'review', 'code review', 'check this change', (3) any automated review action runs for this repo.

2026-06-103

dcb-expert

MateuszNaKodach/HeroesOfDomainDrivenDesign.EventSourcing.DCB.Kotlin.Axon5.Spring

Subject matter expert on Dynamic Consistency Boundary (DCB) — a technique for enforcing consistency in event-driven systems without rigid transactional boundaries. Use when the user asks about DCB concepts, specification, patterns, examples, or compares DCB with traditional Event Sourcing approaches (aggregates, event streams, sagas). Covers topics including tags, projections, decision models, append conditions, queries, and the DCB-compliant Event Store interface. Implementation-agnostic — explains concepts without adhering to any specific library or language.

2026-05-283

em-proophboard-spec

MateuszNaKodach/HeroesOfDomainDrivenDesign.EventSourcing.DCB.Kotlin.Axon5.Spring

Work with proophboard Event Modeling boards via MCP. Read, create, and modify event models — chapters, lanes, slices, and elements (commands, events, information, automations, UI, hotspots). Use when: (1) user asks to read, explore, or understand an event model on proophboard, (2) user asks to create or modify chapters, slices, or elements on the board, (3) user asks to model a feature, flow, or bounded context using Event Modeling, (4) user says 'proophboard', 'event model', 'board', 'add slice to board', 'model this on proophboard', 'update the board', (5) translating between code and event model (syncing implementation status with board slices).

2026-05-283

em2code-write-slice-axon5kotlin

MateuszNaKodach/HeroesOfDomainDrivenDesign.EventSourcing.DCB.Kotlin.Axon5.Spring

Implement Event Sourcing write slices using Axon Framework 5, Vertical Slice Architecture, and Event Modeling patterns. A write slice is: Command to decide to Events to evolve to State. Use when: (1) implementing a new write slice / command handler in an AF5 project, (2) migrating/porting a write slice from Axon Framework 4 (Java or Kotlin) to AF5, (3) user provides a specification, Event Modeling artifact, existing tests, or natural language description of a command and asks to implement it, (4) user says "implement", "create", "add", "migrate", "port" a write slice, command handler, or aggregate behavior in an Axon Framework 5 / Vertical Slice Architecture project. Understands AF4 aggregate-based input as one possible source format.

2026-05-283

em2code-automation-slice-axon5kotlin

MateuszNaKodach/HeroesOfDomainDrivenDesign.EventSourcing.DCB.Kotlin.Axon5.Spring

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.

2026-03-143

em2code-read-slice-axon5kotlin

MateuszNaKodach/HeroesOfDomainDrivenDesign.EventSourcing.DCB.Kotlin.Axon5.Spring

Implement read slices (projections + query handlers + REST API + tests) using Axon Framework 5 AxonTestFixture with Spring Boot integration tests. A read slice is: Events projected into a Read Model, queried via QueryGateway. Use when: (1) implementing a new read slice / projection in an AF5 project, (2) migrating/porting a read slice from Axon Framework 4 (Java or Kotlin) to AF5, (3) user provides a read slice specification or Event Modeling artifact and asks to implement it, (4) user says "implement", "create", "add" a read slice, projection, query handler, or read model in an Axon Framework 5 / Vertical Slice Architecture project.

2026-03-143

name

em-proophboard-backup

description

proophboard Backup

Download the full proophboard workspace into local .proophboard/backup JSON files.

Procedure

Run the backup script:

node .proophboard/scripts/backup.mjs

The script reads PROOPHBOARD_API_KEY from .proophboard/.env.local (preferred, gitignored) or .proophboard/.env, falling back to the environment variable.

If the key is missing and .proophboard/.env.local does not exist, ask the user to provide it, then write it to .proophboard/.env.local:

PROOPHBOARD_API_KEY=pb_xxxx

Report the script's stdout output to the user.