event-hub-vs-signals-contract
CommunityChoose the right communication pattern.
AuthorDubDev720
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This Skill helps developers decide on the most appropriate communication method between different parts of their Godot engine project, preventing common architectural pitfalls like excessive global coupling or overly complex signal chains.
Core Features & Use Cases
- Communication Topology Decision: Provides clear guidelines for using direct signals, local event hubs, or autoload buses.
- Decoupling: Facilitates the replacement of tight node-path dependencies with explicit event boundaries.
- Use Case: When building a complex UI system, this Skill helps determine whether UI elements should communicate directly via signals, through a dedicated UI event bus, or via a global autoload for system-wide notifications.
Quick Start
Use the event-hub-vs-signals-contract skill to decide how a new UI notification system should communicate.
Dependency Matrix
Required Modules
None requiredComponents
references
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: event-hub-vs-signals-contract Download link: https://github.com/DubDev720/gdref/archive/main.zip#event-hub-vs-signals-contract Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.