bevy-genre-rts

使い方

インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
必要なツール、認証情報、対応環境を原文で確認します。
入力と成果物を指定し、出力を資料と照合します。

npx skills add https://github.com/thedivergentai/game-design-agentic-skills --skill bevy-genre-rts

開始前の確認

導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。

リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Bevy RTS (thin router)

Genre router. Domain work lives in the Bevy skills below.

When to use

Load this for selection, orders, and groups.

ECS shape

Components hold the genre's per-entity flags as plain data. This file does not name new engine types.
Resources hold run-wide counters (score, wave index, seed) via bevy-data-resources.
Systems read those components on Update or the fixed timestep from bevy-master. Order them with .chain() when a later system must see the result.
Schedule: gameplay mode changes go through bevy-state-machines. Do not invent a genre plugin.

Coming from Godot

Godot idea	Bevy idiom
Genre scene tree	Entities plus the domain skills linked below
Autoload director	A resource, not a singleton node
Signal bus for the loop	bevy-events-messaging

Routing

bevy-input-handling - Selection clicks.
bevy-ai-navigation - Move orders and navigation.
bevy-combat-system - Attacks.
bevy-economy-system - Costs.

Scope

No selection box or formation type was opened.

Expert Knowledge Delta

Target: Bevy 0.20+.

Core ECS types: Component, Resource, Query, Commands, Startup, Update, Fixed / FixedMain (bevy::time), .chain(), Plugin, DefaultPlugins, MinimalPlugins. Messages and observers are an ownership slot. See bevy-events-messaging for their 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 outside the documented set	Check the official docs first	A made-up crate or API

Load references/ecs-ownership.md for the ownership table.

NEVER

Do not pin /0.20.0/ in docs URLs. WHY: links stay on latest; the 0.20 target is stated once in prose.
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: this skill only names documented Bevy crates and modules.

No Godot types in Bevy code. WHY: Bevy code stays idiomatic ECS and uses only documented Bevy APIs.
No invented genre APIs. WHY: Bevy code stays idiomatic ECS and uses only documented Bevy APIs.
Do not pick a physics or net crate here. WHY: Bevy code stays idiomatic ECS and uses only documented Bevy APIs.

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 - API reference and Cargo feature list.
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.

Related Skills

Prerequisites

bevy-master - ECS ownership and schedules.
bevy-ecs-composition - Spawn and query shape.

Complements

godot-genre-rts - Equivalent Godot skill.
bevy-input-handling - Selection clicks.
bevy-ai-navigation - Move orders and navigation.
bevy-combat-system - Attacks.
bevy-economy-system - Costs.

Downstream / consumers

None. This router does not own a second implementation.

Master

bevy-master - Bevy router.

使い方