3d-graphics-and-render…
Use when designing, choosing, or reviewing the rendering layer of any real-time 3D (or 2D-with-lighting) game — the rasterization pipeline, PBR vs stylized/NPR…
Check whether the installed gamestack plugin is behind the marketplace's latest version and update it in place. Use when asked to "upgrade gamestack", "update gamestack", "check for gamestack updates", "is gamestack up to date", "auto update the plugin", "gamestack upgrade", or
$ npx -y skills add rondorkerin/gamestack --skill gamestack-upgrade --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/gamestack-upgradeContext preview
The summary Claude sees to decide when to auto-load this skill.
Check whether the installed gamestack plugin is behind the marketplace's latest version and update it in place. Use when asked to "upgrade gamestack", "update gamestack", "check for gamestack updates", "is gamestack up to date", "auto update the plugin", "gamestack upgrade", or
name: gamestack-upgrade description: Check whether the installed gamestack plugin is behind the marketplace's latest version and update it in place. Use when asked to "upgrade gamestack", "update gamestack", "check for gamestack updates", "is gamestack up to date", "auto update the plugin", "gamestack upgrade", or "what's new in gamestack". Pure plugin-maintenance utility — no design bible, no engine detection, nothing game-specific.
Claude Code's plugin auto-update is a **client-side opt-in**: each user (or org admin) toggles it per marketplace via `/plugin` → Marketplaces → Enable auto-update, and third-party marketplaces like `gamestack` default to **off**. This repo can't flip that switch for anyone. What it *can* ship is a skill that does the check on demand, using the same `claude plugin` CLI surface auto-update uses internally — invoking this skill is the manual equivalent of a successful auto-update pass.
A version report (current → latest, or "already current") plus, if it updated, the relevant `CHANGELOG.md` entries and a reminder to run `/reload-plugins`.
Read **`UPDATE.md`** for the full step-by-step: locate the install, refresh the marketplace, run the update, and report what changed.
> **Never hand-roll the version diff.** `claude plugin update` already computes "is there a newer version" using the same cache-key logic as auto-update — don't parse JSON or compare version strings yourself to decide whether to update; just run it and report what it says.
Start at `UPDATE.md`.
An agentic framework for building games on any platform — for Claude. Like gstack is for software, but for games. Questions, feedback, or just want to follow along: Discord · @metatransformr on X
Repo: rondorkerin/gamestack
Use when designing, choosing, or reviewing the rendering layer of any real-time 3D (or 2D-with-lighting) game — the rasterization pipeline, PBR vs stylized/NPR…
Use when keeping AI-authored or procedurally-generated content coherent at scale — single voice across a corpus, a machine-readable lore bible with a "never…
Use when designing, speccing, or reviewing a character/object motion system in ANY engine — the rig and skeleton, skinning (linear blend vs dual-quaternion,…
Use when making design-level (not asset-production) decisions about how a game looks and reads — readability vs. fidelity, silhouette design, value/contrast as…
Use when designing, tuning, or reviewing combat and game feel — juice/feedback budgets, hit-stop and impact, telegraphing and danger cues, enemy silhouettes…
Use when designing, tuning, or reviewing the difficulty or balance of any game system — encounter tuning, cost curves, dominant-strategy audits, dynamic…