원클릭으로 Manus에서 모든 스킬 실행

gamestack-upgrade

스타23

포크1

업데이트2026년 6월 30일 23:36

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

rondorkerin

rondorkerin/gamestack

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Gamestack Upgrade

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.

When to use this

The user asks if gamestack is current, or asks to update it
Before relying on a skill that might have changed recently (e.g. before a long headless run)
Anytime — it's a read-then-maybe-write check, safe to run speculatively

What it produces

A version report (current → latest, or "already current") plus, if it updated, the relevant CHANGELOG.md entries and a reminder to run /reload-plugins.

The procedure

Read UPDATE.md for the full step-by-step: locate the install, refresh the marketplace, run the update, and report what changed.

The one rule

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.

이 저장소의 다른 Skills

같은 저장소

iteration-loop

rondorkerin/gamestack

Use when bringing any system — visual (terrain/biome/dungeon/town/castle/character/enemy/NPC/spell-fx), systemic (balance/economy/difficulty), or narrative (lore/quests) — up to fidelity with its intended target through repeated cycles, in any engine. Covers the generic Reference → Diff → Prioritize → Generate/Implement → Verify loop, a preview-harness pattern for screenshotting/inspecting a system in isolation, the animation-can't-be-eyeballed-from-one-frame problem (contact-sheet capture), the external-asset/content-request escalation (when generation is the wrong tool — e.g. animations, trees), the two playtesting channels — human playtesters and an AI playtester that self-verifies via logs/screenshots through a "playtester API" — a human-checkpoint/batching pattern for scaling a generated visual change (including a cheap-mockup gate before heavyweight 3D/tileset generation), and an asset-pack organization + browsable-studio/explorer pattern for what gets approved. Also use to diagnose a project that's gen

2026-06-3023

game-design-process

rondorkerin/gamestack

The orchestrator for designing a game end to end. Use when starting or steering a game's design — "I'm making a game", "where do I start", "design this game with me", "what's next in the design", or running headless to take a concept to generated, reviewed content. Engine-agnostic; tuned for procedural / AI-authored games (e.g. a procgen open-world RPG in Godot). Sequences the pipeline and names which knowledge/process skill to pull at each phase. Stops at design/spec — does not write gameplay code.

2026-06-3023

procgen-review

rondorkerin/gamestack

Run this to review a batch of procedurally- or AI-generated game content (dungeons, regions, quests, items, NPCs, lore, history) before it's committed. Stands in for the human designer's eye in a headless generation loop. Runs the oatmeal test (perceptual sameness), the fanfic/retell test (is it worth retelling), a cross-instance sameness scan (structural/thematic duplication), an intentionality gate (who/what/why + completion arc), and an anti-pattern gate. Outputs a structured pass/fail verdict with specific fixes routed back to the generator. Triggers on "review generated content", "check for sameness", "procgen review", "oatmeal test", "is my generated content any good", "gate this content".

2026-06-3023

3d-graphics-and-rendering

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 materials, the forward/deferred/forward+ lighting architecture, global-illumination and shadow choices, culling/LOD/draw-call/overdraw performance budgets, and the post-processing chain (tonemapping, bloom, AO, anti-aliasing). Also use to diagnose a scene that's GPU-bound or CPU-bound, shadow acne or peter-panning, pop-in, overdraw blowout, blown-out or washed-out tonemapping, or content that looks visually incoherent across generated scenes. Triggers on "rendering pipeline", "PBR", "metallic roughness", "deferred vs forward", "forward+", "global illumination", "GI", "lightmaps", "light probes", "SDFGI", "shadow maps", "cascaded shadows", "shadow acne", "peter panning", "frustum culling", "occlusion culling", "LOD", "pop-in", "draw calls", "batching", "instancing", "overdraw", "CPU bound", "GPU bound", "tonemapping", "ACES", "bloom", "SSAO", "ambient o

2026-06-3023

animation-systems

rondorkerin/gamestack

Use when designing, speccing, or reviewing a character/object motion system in ANY engine — the rig and skeleton, skinning (linear blend vs dual-quaternion, the candy-wrapper artifact), forward vs inverse kinematics, IK solvers (two-bone, FABRIK, CCD, look-at), blend trees and blend spaces (1D/2D), animation state machines, additive layers and upper/lower-body splits, ragdoll and active ragdoll, procedural IK foot placement on uneven terrain, secondary motion (spring bones, cloth, hair), motion matching, animation compression and bone-count budgets, root motion vs in-place, and the anticipation/active/recovery timing decomposition with animation-canceling. Also use to diagnose feet that slide or float, a mesh that pinches when it twists, blends that pop or moonwalk, characters that feel animation-locked, or a motion library that blows the memory budget. Triggers on "animation system", "skeletal animation", "skinning", "candy wrapper", "dual quaternion", "rigging", "inverse kinematics", "IK", "foot placement",

2026-06-3023

procedural-geometry

rondorkerin/gamestack

Use when generating or reviewing the GEOMETRY of a game — procedural terrain, meshes, structures, and scatter. Covers noise as the substrate (Perlin/Simplex/value noise, fractal Brownian motion, domain warping), terrain generation (heightfield vs voxel/SDF, marching cubes, dual contouring, hydraulic/thermal erosion, LOD/chunking), structural generation (L-systems, shape grammars, wave function collapse / model synthesis, constraint-based layout), mesh topology correctness (watertight/manifold meshes, inverted normals, winding order, degenerate triangles/UVs, runtime mesh performance and caching), and vegetation/scatter (Poisson-disc/blue-noise placement, slope/altitude/biome masking, GPU instancing). Also use to diagnose terrain that looks like "noise lumps", structures that read as grid-aligned or obviously generated, scatter that clumps or grids, or generated meshes with black/inverted faces and broken collision. Triggers on "procedural terrain", "terrain generation", "Perlin noise", "Simplex noise", "fBm",

2026-06-3023

name

gamestack-upgrade

description

Gamestack Upgrade

When to use this

The user asks if gamestack is current, or asks to update it
Before relying on a skill that might have changed recently (e.g. before a long headless run)
Anytime — it's a read-then-maybe-write check, safe to run speculatively

What it produces

A version report (current → latest, or "already current") plus, if it updated, the relevant CHANGELOG.md entries and a reminder to run /reload-plugins.

The procedure

Read UPDATE.md for the full step-by-step: locate the install, refresh the marketplace, run the update, and report what changed.

The one rule

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.