rust-turn-intent-systems
Build and review turn-based Rust game flow using turn-state enums, phase-specific schedules, intent messages, movement resolution, combat resolution, wait actions, and win/loss states. Use when implementing roguelike turns, tactical action order, ECS message entities, or decoupled input and action systems.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- rust-turn-intent-systems
- license
- MIT
- metadata
- { "tags": "rust,gamedev,turn-based,ecs,intent", "version": "0.1.0", "category": "Rust", "displayName": "Rust Turn Intent Systems" }
- description
- Build and review turn-based Rust game flow using turn-state enums, phase-specific schedules, intent messages, movement resolution, combat resolution, wait actions, and win/loss states. Use when implementing roguelike turns, tactical action order, ECS message entities, or decoupled input and action systems.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 1
- 参考文档references/turn-intent-patterns.md3.4 KB
03 SKILL.md 正文
Rust Turn Intent Systems
Use this skill to make turn-based gameplay deterministic and easy to extend. Separate decision systems from resolution systems: input and AI create intents; movement, combat, inventory, and end-turn systems resolve them.
Core Workflow
- Define the allowed turn phases in one enum.
- Run different system schedules or branches for input, player resolution, monster resolution, and terminal states.
- Convert input and AI decisions into intent components or messages.
- Resolve intents in shared systems so players and monsters use the same rules.
- Remove or mark intents after processing.
- Advance the turn state in one end-turn boundary.
Read Next
Read references/turn-intent-patterns.md for phase design, intent messages,
ordering rules, and review checks.
Source Notes
Guidance is transformed and paraphrased from Hands-On Rust Chapters 7, 8, 9, and 13 and from the official companion source repository. The patterns are generalized for Rust ECS projects and do not require using Legion.
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.