Claude Skills by rondorkerin

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 blo...

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 violate" list, generate-then-rationalize causation, recurring thematic domains so generated figures cohere into arcs, the oatmeal/sameness problem, and the self-review pass that flags drift and duplication. The crux skill for headless / AI-authored games. Triggers on "AI-authored content", "keep it coherent", "single voice", "lore bible",...

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), moti...

Use when making design-level (not asset-production) decisions about how a game looks and reads — readability vs. fidelity, silhouette design, value/contrast as eye-direction, reserved signal colors, visual-language consistency, and how an AI engine keeps a coherent house style across generated content. Triggers on "art direction", "readability", "silhouette", "signal color", "yellow paint", "visual hierarchy", "style guide", "make it readable", "stylization vs realism", "how should the game l...

Use when designing, tuning, or reviewing combat and game feel — juice/feedback budgets, hit-stop and impact, telegraphing and danger cues, enemy silhouettes and role-based rosters, multi-enemy readability, encounter pacing, and high-lethality (Souls-like) commitment/stamina/checkpoint loops. Also use to diagnose combat that feels floaty, noisy, unfair, swarmy, or like a memorization "knowledge check". Triggers on "combat design", "game feel", "juice", "hit-stop", "screen shake", "telegraph", ...

Use when designing, tuning, or reviewing the difficulty or balance of any game system — encounter tuning, cost curves, dominant-strategy audits, dynamic difficulty adjustment (DDA), difficulty settings, and accessibility assists. Also use to diagnose "this is too hard/too easy", "everything feels overpowered", a degenerate meta, a missing difficulty curve, or an accessibility gap. Triggers on "balance", "balancing", "difficulty", "difficulty curve", "dynamic difficulty", "DDA", "dominant stra...

The platform router for the gamestack framework. Use when a game's design is ready to implement, when the target engine is chosen or needs choosing, or when handing off a spec to engine code — "build this in Godot/Unity/Unreal/Three.js", "which engine", "now implement it", "wire the design to code". Routes design phases to gamestack's foundation skills and implementation to the matching engine pack (godot, unreal, unity). Engine-agnostic itself; it decides where work goes.

The foundational design discipline — the spine the rest of the pack cross-links to. Use when judging whether a mechanic is fun, auditing a system for balance, designing difficulty/flow, setting reward schedules, checking player motivation, or diagnosing "my choices don't matter" / "this is grindy" / "this difficulty spike feels cheap". Covers interesting decisions (Sid Meier), flow & difficulty curves, intrinsic/extrinsic motivation (Self-Determination Theory), feedback & agency, and choice a...

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 gamepla...

Use when designing, tuning, or reviewing the moment-to-moment feel of ANY action in ANY genre — responsiveness, input latency, forgiveness windows (coyote time, input buffering), the juice toolkit (hit-stop, screen shake, squash/stretch, particles, easing, sound layering), the 12 animation principles, camera feel, and UI/menu feel. Also use to diagnose controls that feel floaty, laggy, mushy, weightless, or a screen so noisy you can't read game state. Triggers on "game feel", "juice", "juicy"...

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.

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), ...

Use when designing, generating, or reviewing the craft of an individual level, zone, or encounter — layout, wayfinding, structural type, lock-and-key gating, antepieces, arena design, in-level pacing, and the greybox process. Also use to diagnose levels where players get lost, challenge feels unfair, pacing drags, or teaching moments land flat. Triggers on "level design", "level layout", "greybox", "blockout", "wayfinding", "sightlines", "lock and key", "arena design", "encounter design", "th...

Use when designing quests, reactivity, and factions — quest structure beyond fetch-and-return, branching that honors player choice, reactivity systems on a budget (the "facts database"), procedural/radiant quests as a supplement to hand-authored ones, and faction allegiance dilemmas. Also use to diagnose quests that feel like filler or a world that ignores what the player did. Triggers on "quest design", "fetch quest", "branching", "reactivity", "facts database", "radiant quests", "factions",...

Use when designing, reviewing, or generating the introduction to ANY mechanic in ANY genre — the four-beat teaching pattern (introduce→test→combine→twist), show-don't-tell level design, progressive disclosure and scaffolding, the mechanic dependency graph, FTUE (first-time user experience), early retention funnels, and the skill-atom ramp. Also use to diagnose tutorials that are too long, that players skip, or where players quit before reaching the core loop. Triggers on "onboarding", "tutori...

Use when designing, generating, or reviewing the spatial side of an open world — macro-layout and terrain, landmarks and sightlines, biome identity, verticality, navigation/wayfinding, signal color, exploration pull, and spatial pacing (the wonder→fear gradient, tension/release). Also use to diagnose a world that feels empty, samey, or like marker-following "icon vomit". Triggers on "open world", "world map", "world layout", "wayfinding", "triangle rule", "make the world feel alive", "points ...

Use when designing, auditing, or generating the macro arc of an experience — how engagement rises and falls across an encounter, a session, a level, and an entire playthrough. Covers the interest curve and fractal pacing, tension/rest rhythm, novelty cadence and mid-game sag, nested engagement loops and retention ethics, first-hour pacing by genre, and the procedural pacing director algorithm. Triggers on "pacing", "tension curve", "interest curve", "the game drags", "mid-game sag", "player j...

Use when designing high-lethality / permadeath / single-save combat and the systems around it — making death fair and readable, mitigating the cost of failure without removing stakes (short runs, opt-in difficulty, deterministic anti-save-scum), meta-progression and diegetically-integrated death (roguelike vs. roguelite), and the hard open problem of single-save permadeath in a long-form open world. Also use to diagnose deaths that feel unfair, a game churning players at the first big loss, o...

Use when designing or building a content generator — terrain, dungeons, quests, items, lore, history — or diagnosing generated content that feels samey, generic, or soulless. Covers the "10,000 bowls of oatmeal" problem, perceptual vs. mathematical uniqueness, the handcrafted-anchor + constrained-fill hybrid, voice-consistent corpora, multiplicative systems, and tying generation to meaning. Core skill for headless / AI-authored games. Triggers on "procedural generation", "procgen", "generator...

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...

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 ver...

Use when designing, tuning, or reviewing the core RPG systems triad — character progression (leveling, skills, attributes, classless vs. class), the economy (currencies, faucets/sinks, crafting materials), and loot & itemization (rarity tiers, drop rates, legendary/unique design). Also use to diagnose "leveling feels pointless", "the world scales with me", "players hoard their best items", "every legendary is just +stats", "the economy inflated", or "more loot but it means less". Triggers on ...

Use when authoring shaders/materials or building visual effects in ANY engine — the shader model (vertex/fragment/compute, what each reads and writes), node-graph material thinking, procedural texturing (noise, SDFs, triplanar, vertex-color/splat masks) vs. baked textures, the VFX toolkit (CPU vs GPU particles, trails/ribbons, decals, distortion/refraction, dissolve/hit-flash/rim effects), stylized rendering (toon/cel shading, outline rendering via inverted hull or post-process edge detection...

Use when designing, auditing, or generating the systemic substrate of a game — the small set of consistent, interacting rules (a "chemistry engine") that produce emergent play, rather than scripted set-pieces. Covers immersive-sim principles (intention & perceivable consequence), multiplicative vs. additive design, the "tabletop RPG with a good GM" analogy, and how emergent systems make procedural generation cohere instead of becoming "oatmeal". Also use to diagnose "the world feels inert", "...

Use when designing, auditing, or generating a HUD, menu system, or feedback vocabulary for any genre — information hierarchy, diegetic vs. non-diegetic classification, cognitive load budgeting, feedback channel design, menu flow, input modality, and accessibility. Also use to diagnose a UI that is cluttered, that players ignore, that confuses state, or where players miss critical information. Triggers on "UI", "UX", "HUD", "menus", "interface", "diegetic UI", "non-diegetic", "information hier...

Use when building a world bible and deciding how lore reaches the player — the iceberg principle (author the whole world, surface ~10%), environmental & item-description storytelling, an "alien but coherent" identity that survives procedural generation, deep history as faction-proxy pantheons, and ludonarrative harmony (mechanics that are the story). Also use to diagnose lore that info-dumps, feels generic-fantasy, or has gaps that read as contradictions rather than mystery. Triggers on "worl...