Bevy Testing Patterns

Community

thedivergentai

bevy-testing-patterns

Docs-first stub for Cargo tests around Bevy work. Godot counterpart: godot-testing-patterns. Not a GdUnit port. Keywords: Bevy, cargo test, Rust, libtest.

Overview

Publisher	thedivergentai
Repository	`Game-Design-Agentic-Skills`
Skill name	`bevy-testing-patterns`
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 Testing Patterns 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-testing-patterns
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-testing-patterns

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-testing-patterns .claude/skills/bevy-testing-patterns

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

Use it in TypingMind

Enable Bevy Testing Patterns 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 Testing Patterns 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 Testing Patterns 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 testing patterns (docs-first stub)

Not a full port. Tests here are Cargo's test harness. There is no GdUnit twin.

When to use

Load this when a Bevy crate needs unit or integration tests. The Cargo book page for cargo test (opened 2026-10-11) is the source. A current Bevy "how to App::update inside #[test]" page was not opened, so that recipe stays a gap.

ECS shape

Command: cargo test compiles and runs unit tests, integration tests, and documentation tests. cargo test name_filter runs names that contain the filter. Arguments after -- go to libtest (cargo test -- --help).
What runs: functions annotated with #[test]. The harness runs them in multiple threads. The working directory for each test is the package root, so relative paths resolve from that root no matter where you invoked Cargo.
Scope: default cargo test covers the lib, bins as unit tests, integration tests, and doc tests, and it builds examples. --lib limits to the library. harness = false on a target means you supply main.
Profile: the test profile is the default. --profile=debug keeps debug info. -- --no-capture shows test output.
Bevy types inside a test: not specified here. Do not copy an App::new() test from an old discussion. Bevy's own crates contain #[cfg(test)] modules; their helpers were not opened as a public guide.

Godot idea to Bevy idiom

Idea	Bevy idiom (idea only)
Run the suite	`cargo test` from the package
One test name	`cargo test name_filter`
See prints	`cargo test -- --no-capture`
Scene-tree test runner	No twin. GdUnit stays on the Godot skill

Gaps

No docs.rs latest page was opened that shows App, MinimalPlugins, and app.update() inside #[test]. Do not invent that harness.
Headless frame capture, golden images, and input injection for tests were not opened.
Doctest working-directory rules differ from unit tests (workspace root for rustdoc compile). Do not assume a doctest can read assets/ the same way.

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 GdUnit, GUT, or Godot test-runner types. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
No App::update test recipe this file did not open. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.
No third-party Bevy test 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.
cargo test - #[test], filters, libtest args, package root as cwd.
Examples - Example tree on the latest branch. Examples are not the test harness.

Related Skills

Prerequisites

bevy-master - Who owns which piece of state.
bevy-project-foundations - The Cargo package cargo test runs against.

Complements

godot-testing-patterns - Godot counterpart. GdUnit stays there.

Downstream / consumers

None yet.

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 Testing Patterns AI skill do?

Docs-first stub for Cargo tests around Bevy work. Godot counterpart: godot-testing-patterns. Not a GdUnit port. Keywords: Bevy, cargo test, Rust, libtest.

Why use Bevy Testing Patterns on TypingMind?

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

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

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 Testing Patterns?

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

Is the Bevy Testing Patterns 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

Autoreview

openclaw

OrganizationPopular

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Control Ui E2e

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Bevy testing patterns (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