Bevy Adapt Mobile To Desktop logo

Bevy Adapt Mobile To Desktop

Community
thedivergentai
bevy-adapt-mobile-to-desktop

Docs-first stub for adapting a Bevy mobile game to desktop. Godot counterpart: godot-adapt-mobile-to-desktop. Keywords: Bevy, desktop, mouse, keyboard, adapt, window.

Overview

Publisherthedivergentai
RepositoryGame-Design-Agentic-Skills
Skill namebevy-adapt-mobile-to-desktop
Stars
834
Forks
53
Bundled files
1
LicenseLGPL-3.0
Links
  • 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 Adapt Mobile To Desktop AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/thedivergentai/Game-Design-Agentic-Skills/tree/main/skills/bevy-adapt-mobile-to-desktop
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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-adapt-mobile-to-desktop .claude/skills/bevy-adapt-mobile-to-desktop
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bevy Adapt Mobile To Desktop 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 Adapt Mobile To Desktop 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 Adapt Mobile To Desktop 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 adapt mobile to desktop (docs-first stub)

Not a full port. Docs-first stub. Godot counterpart: godot-adapt-mobile-to-desktop.

When to use

Load this when a touch-first game gains a window, mouse, and keyboard. Window setup is bevy-platform-desktop.

ECS shape

  • Window: Window, WindowMode, and PrimaryWindow.
  • Input: keyboard, mouse, and gamepad features are named on the crate page and already used by bevy-input-handling.
  • Cursor: CursorGrabMode and CursorOptions are on the window page. Grab semantics were not opened.

Godot idea to Bevy idiom

IdeaBevy idiom (idea only)
Touch buttonsKeyboard and mouse via bevy-input-handling.
Portrait layoutA wider Node tree. No orientation type was opened.
Cursor lockCursorGrabMode exists. Variants were not opened.

Gaps

  • Hint glyphs and control prompts were not opened.
  • Cursor grab mode variants 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

PieceOwnerWho may mutateSchedule
Data on one entityComponentOne system via QueryUpdate or FixedMain
One value for the whole appResourceOne systemStartup to insert, then the schedule that reads it
SpawnCommandsThe spawning systemStartup for the initial world; later schedules for runtime spawn
Order that must not race.chain()The chained systems onlySame schedule
Plugin boundaryPluginbuild registers systems and resourcesBefore 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 needDo thisDo not
Per-entity dataComponent + QueryA Godot node script
App-wide config or clockResourceCopy the value onto every entity
Stable simulation stepFixedMain and the Fixed clockTie simulation to raw frame Update
Startup spawnCommands in StartupSpawn from a render system
Cross-system notice that is not shared stateMessage or observer slot in bevy-events-messagingA new event type invented in this file
An API this skill did not openA Gaps rowA 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 device-feature tags. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

  • No Godot types in Bevy code. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

  • No invented APIs or unnamed third-party crates as the chosen solver. 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. Feature list opened for 0.20.0.
  • Assets - Official asset catalog. No third-party crate was selected.
  • Examples - Example tree on the latest branch.
  • ECS - Component, systems, Query, Startup, Update, and .chain().
  • Plugins - Plugin, DefaultPlugins, MinimalPlugins, and add_plugins.
  • bevy::window - CursorGrabMode, WindowMode.

Related Skills

Prerequisites
Complements
Downstream / consumers
  • None yet.
Master

Bundled files

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

Frequently asked questions

What does the Bevy Adapt Mobile To Desktop AI skill do?

Docs-first stub for adapting a Bevy mobile game to desktop. Godot counterpart: godot-adapt-mobile-to-desktop. Keywords: Bevy, desktop, mouse, keyboard, adapt, window.

Why use Bevy Adapt Mobile To Desktop on TypingMind?

Because you install it once and use it with any model. Bevy Adapt Mobile To Desktop 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 Adapt Mobile To Desktop in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thedivergentai/Game-Design-Agentic-Skills/tree/main/skills/bevy-adapt-mobile-to-desktop. 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 Adapt Mobile To Desktop?

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 Adapt Mobile To Desktop?

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

Is the Bevy Adapt Mobile To Desktop 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇