菜单
Create git commits following project conventions: Conventional Commits + Gitmoji with Unicode emojis. Use when: (1) user says 'commit', '/commit', 'create a commit', (2) user asks to commit changes, (3) user asks for a commit message, (4) after completing implementation work and user wants to commit.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | commit |
| description | Create git commits following project conventions: Conventional Commits + Gitmoji with Unicode emojis. Use when: (1) user says 'commit', '/commit', 'create a commit', (2) user asks to commit changes, (3) user asks for a commit message, (4) after completing implementation work and user wants to commit. |
Create git commits following project conventions: Conventional Commits + Gitmoji.
<emoji> <type>(optional-scope): <description>
✨), never shortcodes (e.g. :sparkles:)`BuildDwelling`)Co-Authored-By, etc.)| Emoji | Type | When to use |
|---|---|---|
| ✨ | feat | New feature or slice implementation |
| 🐛 | fix | Bug fix |
| ♻️ | refactor | Code refactoring (no behavior change) |
| 🏗️ | refactor(architecture) | Architectural restructuring |
| ✅ | test | Adding or updating tests |
| 🧪 | chore(tests) | Test infrastructure/configuration |
| 📦 | build(deps) | Dependency additions or upgrades |
| ⬆️ | deps | Dependency version upgrades |
| 🐳 | chore(docker) | Docker and container configuration |
| 👷 | ci | CI/CD pipeline changes |
| 📝 | docs | Documentation |
| 🔧 | config(scope) or chore(scope) | Configuration changes |
| 🎉 | chore | Project initialization |
| 🔥 | remove | Removing code or files |
| 🤖 | ai-agent(scope) | AI coding agent config (skills, CLAUDE.md, prompts) |
| ✨ | feat(mcp) | MCP server features (tools, resources) |
| 🧑💻 | chore(dx) | Developer experience improvements |
| 📸 | chore | Snapshotting configuration |
| 🪲 | chore(debugging) | Debugging helpers (log levels, etc.) |
| 🚀 | feat(scripts) | Deployment or utility scripts |
When implementing a slice from Event Modeling, use ✨ feat: with bounded context, slice type, and flow:
✨ feat: <BoundedContext> | write slice: <CommandName> -> <EventName(s)>
✨ feat: <BoundedContext> | read slice: (<EventName(s)>) -> <ReadModelName>
✨ feat: <BoundedContext> | automation: <EventName> -> <CommandName>
✨ feat: <BoundedContext> | write slices: <CommandName1> and <CommandName2>
Examples:
✨ feat: Creature Recruitment | write slice: BuildDwelling -> `DwellingBuilt`
✨ feat: Creature Recruitment | write slice: RecruitCreature -> (`CreatureRecruited`, `AvailableCreaturesChanged`)
✨ feat: Creature Recruitment | read slice: (`CreatureRecruited`, `AvailableCreaturesChanged`) -> `GetAllDwellings`
✨ feat: Creature Recruitment | automation: `CreatureRecruited` -> `AddCreatureToArmy`
✨ feat: Astrologers | write slice: `ProclaimWeekSymbol` -> `WeekSymbolProclaimed`
✨ feat: Calendar | write slices: `StartDay` and `FinishDay`
# ai-agent = AI coding agents that help develop the project
🤖 ai-agent(claude-code): init with `CLAUDE.md`
🤖 ai-agent(skills): update AF5 slice documentation
# feat(mcp) = AI as a product feature in the app
✨ feat(mcp): add MCP server
✨ feat(mcp): `BuildDwelling` write slice | add MCP server tool
git status and git diff --staged (and git diff if needed) to understand changesgit log --oneline -5 to see recent commit stylegit add -A)git commit -m "$(cat <<'EOF'
<emoji> <type>(scope): <description>
EOF
)"
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.
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.
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).
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.
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.
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.