Modify a game level from a design brief

Using Codex CLI where available: Supply an existing game copy and level requirements to make a bounded change with test evidence and unfinished work.

Execution environment and usage

AI / software

Codex CLI (suggested exercise route; original stack differs)

Where to operate

Codex CLI in a terminal with an isolated authorized project copy. This suggested route is not the same installable system as the original research setup.

Getting started

  1. Follow the linked official Codex setup guide, sign in and start Codex in the test project folder.
  2. Open a test branch of your game and confirm its baseline runs.
  3. Supply the level design and bounded scope, then use the prompt.
  4. Run project checks and playtest manually; list unfinished work.

Setup and plan requirements

Existing game, compatible dependencies and licensed assets; the original custom harness is not fully specified. Requires Codex access and compatible project tools/versions. Authorize only necessary files and commands, without production-service connections.

Prompt portability limits

Model name does not identify Grok Bot or a runnable consumer workflow. Existing interfaces/assets are essential.

Usage limitations

This review performed no installation, hands-on test or regional-availability check. Original poster names Grok 4.5, detailed design document, existing game level and manual cleanup.

Environment sources

適用情境 / When to use

This suits developers extending a working project. It needs repository access and a compatible development setup. Loading the level is only one check; routes, collisions and controls still need playtesting. aniketjatav reports using Grok 4.5 and a custom harness to add a level to an existing game, followed by manual cleanup.

步驟 / Steps

  1. Prepare an owned game copy, design specification and working development environment.
  2. Express goals, routes, interactions and failure conditions as checks while preserving existing interfaces.
  3. Manually test reachability and collisions, recording unfinished work beyond successful loading.

提示詞 / Prompt

Implement [bounded scope] from [level design document] in [owned game test branch], preserving [controls, style and difficulty requirements]. List acceptance checks, test evidence and unfinished work. Add no unrequested features, publish nothing and use no unlicensed assets.

留意事項 / Cautions

  • Use licensed assets and sound effects.
  • Running code does not establish fairness or fun.

來源限制 / Evidence limits

The source confirms the model and custom harness, not the Grok Bot product; no player or performance evaluation is given.

流程說明 / Workflow note

These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.

原始工具組合 / Original tool stack

Grok 4.5 model; custom game-development harness; Three.js

Source checked: 2026-10-19

Built this game using Grok 4.5, Threejs and my game dev harness