Individual skill

rust-legion-ecs-gameplay

Design and review Rust ECS gameplay code using Legion-style entities, components, resources, systems, schedules, queries, command buffers, and spawners. Use when building ECS-driven Rust game features, migrating game state into ECS, or debugging system ordering and component composition.

plugins/LVTD-LLC/skills/skills/rust-legion-ecs-gameplay/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,535
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Rust Legion ECS Gameplay

Use this skill to build ECS gameplay code in Rust, especially in projects using
Legion or a Legion-like architecture. Keep components as data, systems as
focused logic, and resources as shared singleton state.

## Core Workflow

1. Identify entities, components, systems, and resources from the feature.
2. Add data-only components before adding systems that consume them.
3. Put entity construction in spawner functions or factories.
4. Use queries that request only the components a system needs.
5. Sequence systems with schedules and flush points when later systems must
   observe structural changes.