MuharremTozan/Agentic-Duel / .agent/skills/unity-event-bus
unity-event-bus
VerifiedAdvanced code-driven event bus with reflection-based bootstrapping. Provides zero-setup global messaging.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
| assets/code/EventBusBootstrapper.cs.txt | markdown | 2.0 KB |
| assets/code/EventBusCore.cs.txt | markdown | 1.6 KB |
| assets/code/EventBusExample.cs.txt | markdown | 1.3 KB |
| assets/docs/Checklist.md.txt | markdown | 950 B |
| references/guide.md | markdown | 1.6 KB |
assets/docs/Checklist.md.txt
View on GitHub# Event Bus Implementation Checklist
Use this checklist during a `/smart-review` to ensure the Event Bus is implemented correctly.
## 1. Event Definition
- [ ] Is the event a `struct`? (Mandatory for zero-allocation).
- [ ] Does it implement `IEvent`?
- [ ] Is the name descriptive (e.g., `PlayerDiedEvent` instead of `Death`)?
## 2. Subscription Lifecycle
- [ ] Is the `EventBinding<T>` cached as a field?
- [ ] Is it registered in `OnEnable` using `EventBus<T>.Register(binding)`?
- [ ] **CRITICAL**: Is it unregistered in `OnDisable` using `EventBus<T>.Unregister(binding)`?
## 3. Propagation
- [ ] Is `EventBus<T>.Raise(newEvent)` used for dispatching?
- [ ] Are listeners performing heavy logic? (Favor queuing or async if the logic is complex).
## 4. Architecture
- [ ] Is the Event Bus replacing a direct reference between two Managers? (If so, good job).
- [ ] Are we avoiding "Event Chains" (Event A triggers Event B triggers Event C)?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |