Skip to main content
prompt GP ChatGPT

reference-to-game — Claude Code prompt for reference-based games

reference-to-game — a prompt for Claude Code that guides game creation from supplied references and a brief. The agent inspects the source files, builds a playable loop, then compares the scene with the visual references.

MIT ★ 71 updated 2026-11-13

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gokayfem/reference-to-game
/plugin install reference-to-game@reference-to-game
Open on GitHub

What reference-to-game does

The prompt lays out a workflow for building a game from supplied references and a brief. The agent inspects the actual files first and identifies which sources describe the look, mechanics, motion and interface. It then creates a small scene with an action and HUD, compares it with the references, and fixes the most visible mismatches.

The workflow continues with controls, game state, goals, feedback and restart. Game rules stay separate from rendering, while counters and UI reflect the game state. The prompt calls for testing a full session, the production build and performance. Deliverables include editable source, a gameplay recording and validation evidence.

Asset generation through fal is subject to the user's authorization and budget; generation credentials must stay out of client code. Publishing requires authorization. For a case-specific prompt, run python3 skills/reference-to-game/scripts/r2g.py prompt PATH_TO_CASE --out IMPLEMENT.txt.

What it helps with

  • build a playable scene from visual references
  • connect controls, game state and HUD
  • test a complete session through restart
  • compare a finished scene with its references

Example prompts for the agent

  • Build a small playable game from these references and the brief; inspect the actual files first.
  • Implement controls, goals, a HUD and restart using the supplied materials.
  • Compare the scene with the references, fix the largest visual mismatches and record a playthrough.

How to install reference-to-game

1Plugin marketplace

/plugin marketplace add gokayfem/reference-to-game
/plugin install reference-to-game@reference-to-game

2Manually: put the files in place

.claude/commands/reference-to-game.md

Questions about reference-to-game

How do I install reference-to-game in Claude Code?

Run /plugin marketplace add gokayfem/reference-to-game, then /plugin install reference-to-game@reference-to-game. The plugin command file is .claude/commands/reference-to-game.md.

What does reference-to-game do?

It guides an agent from inspecting game references through building and testing a playable scene. It also calls for source files, a gameplay recording and validation evidence.

What applies to generated assets in reference-to-game?

Asset generation must follow the user's authorization and budget. Generation credentials must not go into client code.

Source text

reference-to-game.md · MIT
# Reference-to-game implementation prompt

Use the reference-to-game skill in this repository. Build a genuinely playable game from the supplied references and brief. Inspect the actual files first and identify which sources govern appearance, identity, mechanics, motion and UI. Preserve originals and distinguish observations from inferences and deliberate design choices. A link or a filename alone is not inspected evidence.

Style and colors are the first priority. Preserve semantic color relationships and coverage, silhouettes, proportions, materials, lighting, camera framing, motion language and interface. Choose 2D, 2.5D, 3D or a hybrid according to what best preserves the input. Do not impose a default bright low-poly style, fixed grid, nine scenes or a familiar game template. Build one small polished scene with a real action and HUD, compare it against the reference, and correct the largest visible mismatches before expanding scope.

Implement a coherent loop with actual input, state changes, feedback, goals, recovery and restart. Author missing rules explicitly instead of copying generated-video mistakes. Separate game rules from rendering; keep counters and UI tied to state; use stable entity/reward IDs. Follow the user's engine and platform constraints. Test a complete session through the actual controls and record it.

Use existing, procedural or fal-generated assets when they improve fidelity. Honor the user's generation authorization and budget. Verify current endpoint schemas, keep identity anchors throughout edits, prepare isolated assets for 3D generation, and inspect the results under runtime lighting. Save request IDs before polling, reconcile uncertain submissions and reuse accepted outputs. Never expose generation credentials in client code.

Work through visual refinement, production build, input-driven playthrough, restart and measured performance. Deliver editable source, controls, lockfile, runtime assets and provenance, reference comparisons, gameplay recording, validation evidence and honest limitations. Continue autonomously through normal reversible implementation work; do not stop at a plan, attractive screenshot or compile success. Do not publish without authorization.

For a concrete case-specific prompt, run `python3 skills/reference-to-game/scripts/r2g.py prompt PATH_TO_CASE --out IMPLEMENT.txt`.

© gokayfem · MIT · gokayfem/reference-to-game

Similar prompts

All prompts for Game dev and 3D: Unity, Unreal, Godot, Blender →

From the same set3

Project sponsors

Companies that keep this analytics open