Bevy Events Messaging

Community

thedivergentai

bevy-events-messaging

Docs-first stub for Bevy messages and observers. Godot counterpart: godot-signal-architecture. Not a full port. Keywords: Bevy, Message, Event, Observer.

Overview

Publisher	thedivergentai
Repository	`Game-Design-Agentic-Skills`
Skill name	`bevy-events-messaging`
Stars	834
Forks	53
Bundled files	1
License	LGPL-3.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by thedivergentai on GitHub. Read the source before you install it.

Installation

Install the Bevy Events Messaging AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/thedivergentai/Game-Design-Agentic-Skills/tree/main/skills/bevy-events-messaging
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/thedivergentai/Game-Design-Agentic-Skills/tree/main/skills/bevy-events-messaging

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/thedivergentai/Game-Design-Agentic-Skills.git /tmp/Game-Design-Agentic-Skills
mkdir -p .claude/skills
cp -r /tmp/Game-Design-Agentic-Skills/skills/bevy-events-messaging .claude/skills/bevy-events-messaging

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bevy Events Messaging in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bevy Events Messaging on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bevy Events Messaging is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Bevy events and messaging (docs-first stub)

Not a full port. Two opened mechanisms: buffered messages, and events that run observers immediately. Neither is a signal bus.

When to use

Load this when one system should notice that something happened without storing that fact on every entity. Pick the mechanism from the pages below. Do not invent a third channel.

ECS shape

Messages (pull). bevy::ecs::message 0.20.0 defines the Message trait as a buffered message for pull-based handling. MessageWriter writes. MessageReader reads and tracks what it already saw. Messages holds what occurred within the last two Messages::update calls. message_update_system calls Messages::update on registered messages. signal_message_update_system signals that update after FixedUpdate systems. Registration helpers on App were not opened. Do not invent an add_message name.
Events (push). The Event trait page: derive Event, add an observer, trigger. The sample uses World::trigger and world.add_observer with On<Speak>. Commands::trigger is also named. Observers run immediately inside the trigger call. Event::Trigger defaults to GlobalTrigger for derived events.
Observers. bevy::ecs::observer: an Observer is a component that holds a system. On is the system parameter that processes the event. EntityEvent is the page's pointer for events that target one entity. The entity-event trait page was not opened.
State transitions. bevy::state documents StateTransitionEvent<S> when state S changes. That type lives with states. See bevy-state-machines.

Godot idea to Bevy idiom

Idea	Bevy idiom (idea only)
Something happened; readers poll later	A `Message` plus `MessageWriter` / `MessageReader`
Something happened; listeners run now	An `Event` plus an `Observer` (`On<...>`) and `trigger`
Notice on one entity	`EntityEvent` (trait page not opened; do not invent methods)
Global signal singleton	Not this. Use a message type or a global event

Gaps

App methods that register a message type were not opened.
EntityEvent methods, entity-targeted trigger helpers, and observer run-condition helpers were not opened beyond the module index names.
Ordering between message_update_system and gameplay systems was not opened beyond the FixedUpdate signal function name.

Expert Knowledge Delta

Library target in prose: Bevy 0.20.0. Lattice URLs stay unversioned.

Opened canon only: Component, Resource, Query, Commands, Startup, Update, Fixed / FixedMain (bevy::time), .chain(), Plugin, DefaultPlugins, MinimalPlugins. Messages and observers are an ownership slot. This file does not invent their struct APIs. Systems run in parallel unless .chain() orders the ones that conflict.

Who owns state

Piece	Owner	Who may mutate	Schedule
Data on one entity	`Component`	One system via `Query`	`Update` or `FixedMain`
One value for the whole app	`Resource`	One system	`Startup` to insert, then the schedule that reads it
Spawn	`Commands`	The spawning system	`Startup` for the initial world; later schedules for runtime spawn
Order that must not race	`.chain()`	The chained systems only	Same schedule
Plugin boundary	`Plugin`	`build` registers systems and resources	Before the app runs

Borrow rule: two systems that both mutably query the same component must be ordered (.chain()) or split so only one writes. Unrelated systems stay parallel. That is the ECS page rule, not a guess at a system-set API.

Decision

If you need	Do this	Do not
Per-entity data	`Component` + `Query`	A Godot node script
App-wide config or clock	`Resource`	Copy the value onto every entity
Stable simulation step	`FixedMain` and the `Fixed` clock	Tie simulation to raw frame `Update`
Startup spawn	`Commands` in `Startup`	Spawn from a render system
Cross-system notice that is not shared state	Message or observer slot in `bevy-events-messaging`	A new event type invented in this file
An API this skill did not open	A Gaps row	A fabricated crate (solver, navmesh module, net, XR)

Load references/a-gate-notes.md for the same table plus the gap rule.

NEVER

Do not put /0.20.0/ in lattice URLs. WHY: permalinks stay on latest. The 0.20.0 pin belongs in prose once.
Do not mutably query the same component from two unordered systems. WHY: the schedule runs systems in parallel unless .chain() orders them.
Do not invent a physics, navigation, networking, or XR crate here. WHY: those rows are gaps, blocked, or revisit.
No Godot signal types or a signal bus autoload. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
No invented message-registration or trigger methods. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
No third-party crates. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
No Creation Station content. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
No umbrella skill over Godot and Bevy. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
Do not mark this row ported. It is docs_mapped. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

Reference

docs.rs links use the unversioned latest permalink. The library pin on bevy-master stays 0.20.0.

Official Documentation

Migration guides - Unversioned hop index.
bevy crate - Unversioned API index.
bevy::ecs::message - Message, MessageWriter, MessageReader, Messages, message_update_system.
Event - Event, On, World::trigger, Commands::trigger, add_observer.
bevy::ecs::observer - Observer and On.
Examples - Example tree on the latest branch.

Related Skills

Prerequisites

bevy-master - ECS ownership before adding a notice channel.
bevy-ecs-composition - Systems that write or read the notice.

Complements

bevy-state-machines - StateTransitionEvent for app-wide state changes.
godot-signal-architecture - Godot counterpart. Source idea only. Do not import Godot types.

Downstream / consumers

None yet. Gameplay skills are not ported.

Master

bevy-master - Bevy router.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/a-gate-notes.md1 KB

Frequently asked questions

What does the Bevy Events Messaging AI skill do?

Docs-first stub for Bevy messages and observers. Godot counterpart: godot-signal-architecture. Not a full port. Keywords: Bevy, Message, Event, Observer.

Why use Bevy Events Messaging on TypingMind?

Because you install it once and use it with any model. Bevy Events Messaging is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bevy Events Messaging in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thedivergentai/Game-Design-Agentic-Skills/tree/main/skills/bevy-events-messaging. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Bevy Events Messaging?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bevy Events Messaging?

As many as you like. As long as a model supports skills, you can use Bevy Events Messaging with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bevy Events Messaging AI skill free?

Yes. It is published on GitHub by thedivergentai under the LGPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Migration

NousResearch

OrganizationPopular

Import an OpenClaw setup (memories, skills) into Hermes.

Doc Coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This…

Caveman Discover

Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

Complain

Autonomously yeet a brief, unstructured complaint about agent tooling or doing agent work. Preserve the raw voice. Submit proactively without permission, preview, or announcement, then continue the…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Bevy events and messaging (docs-first stub)

When to use

ECS shape

Godot idea to Bevy idiom

Gaps

Expert Knowledge Delta

Who owns state

Decision

NEVER

Reference

Official Documentation

Related Skills

Prerequisites

Complements

Downstream / consumers

Master

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now