Bevy Input Handling

Community

thedivergentai

bevy-input-handling

Docs-first stub for Bevy player input. Godot counterpart: godot-input-handling. Not a full port. Keywords: Bevy, ButtonInput, KeyCode, MouseButton, Gamepad.

Overview

Publisher	thedivergentai
Repository	`Game-Design-Agentic-Skills`
Skill name	`bevy-input-handling`
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 Input Handling 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-input-handling
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-input-handling

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-input-handling .claude/skills/bevy-input-handling

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

Use it in TypingMind

Enable Bevy Input Handling 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 Input Handling 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 Input Handling 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 input handling (docs-first stub)

Not a full port. Input here is resources and events on the app, not an action map copied from Godot.

When to use

Load this when a system should read keyboard, mouse, or gamepad state. The bevy::input module (docs.rs latest, crate 0.20.0) is the source for the names below.

ECS shape

Plugin: InputPlugin adds input from keyboard, mouse, gamepad, and touch. It ships inside the usual app plugins. InputSystems labels the systems that refresh that data.
Keyboard resource: Res<ButtonInput<KeyCode>>. KeyCode is the physical key (layout-stable). Res<ButtonInput<Key>> is the logical key. The keyboard example uses pressed, just_pressed, and just_released.
Mouse: mouse_button_input_system writes ButtonInput<MouseButton> from MouseButtonInput. AccumulatedMouseMotion and AccumulatedMouseScroll are resources reset every frame. MouseMotion and MouseWheel are the underlying events.
Gamepad: Gamepad stores a connected pad's metadata (GamepadButton, GamepadAxis). Connection and axis changes arrive as GamepadConnectionEvent, GamepadAxisChangedEvent, and GamepadButtonChangedEvent. GamepadRumbleRequest is the force-feedback event.
Schedule: read these resources from a system on Update (or a schedule you already chain). Do not invent an input-map resource.

Godot idea to Bevy idiom

Idea	Bevy idiom (idea only)
Action just pressed	`ButtonInput::just_pressed` on `KeyCode` or `MouseButton`
Action held	`ButtonInput::pressed`
Physical WASD vs symbol keys	`KeyCode` for location, `Key` for the character
Mouse look delta	`AccumulatedMouseMotion` (reset each frame)
Controller	`Gamepad` plus the gamepad events listed above

Gaps

Touch and gesture modules are listed on the input index. Their event fields were not opened.
A project-wide action-map resource (named actions, rebinding) was not opened. Do not invent one.
Glyphs and device prompts were not opened.

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 input-map, event, or device types. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
No APIs this file did not open (pressed, just_pressed, just_released are the button methods cited). WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
No third-party input 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::input - ButtonInput, InputPlugin, device modules.
ButtonInput - pressed, just_pressed, just_released, KeyCode and Key.
Mouse - MouseButton, motion and scroll resources.
Gamepad - Gamepad and connection events.
Examples - Example tree on the latest branch.

Related Skills

Prerequisites

bevy-master - Who owns which piece of state.
bevy-ecs-composition - Systems and Query.

Complements

bevy-character-movement - Motion that consumes this input on the fixed timestep.
bevy-camera-systems - Viewpoint that may read mouse motion.
godot-input-handling - Godot counterpart. Source idea only.

Downstream / consumers

bevy-audio-systems - The audio control example reads ButtonInput<KeyCode> to pause and mute.

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 Input Handling AI skill do?

Docs-first stub for Bevy player input. Godot counterpart: godot-input-handling. Not a full port. Keywords: Bevy, ButtonInput, KeyCode, MouseButton, Gamepad.

Why use Bevy Input Handling on TypingMind?

Because you install it once and use it with any model. Bevy Input Handling 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 Input Handling in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thedivergentai/Game-Design-Agentic-Skills/tree/main/skills/bevy-input-handling. 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 Input Handling?

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 Input Handling?

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

Is the Bevy Input Handling 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

Version Bump

thedotmack

CommunityPopular

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging,…

Agent Builder

Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or…

Changelog Generator

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns…

Agent Authentication

Agent skill for authentication - invoke with $agent-authentication

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Bevy input handling (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