Individual skill

rust-bracket-game-loop

Build and review bracket-lib style Rust 2D game loops, state structs, game modes, input handling, rendering calls, and restart flow. Use when creating a small Rust game with bracket-lib, porting a tutorial loop, or debugging tick/update/render state behavior.

plugins/LVTD-LLC/skills/skills/rust-bracket-game-loop/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,532
Repository last updated
Nov 6, 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 Bracket Game Loop

Use this skill to create or review a small Rust game loop, especially one built
with `bracket-lib` and an explicit game state. Keep `tick` as a coordinator:
read input, advance state, render, and dispatch to small helper functions.

## Core Workflow

1. Inspect the target project's `Cargo.toml`, edition, engine, and existing
   architecture before changing dependencies.
2. Create one state object that contains data preserved between frames.
3. Implement the engine trait or callback required by the project.
4. Route modes through an enum rather than scattered booleans.
5. Keep rendering and state mutation ordered and easy to trace.