Tag
5 pages tagged “Prompting”.
5 pagesClear filters
A fill-in brief you paste into a coding model at the start of a game: loop, controls, rules, camera, feel numbers, scope cuts and acceptance tests, plus working rules that make it ask questions first, plan milestones and build one verified step at a time.
A four-part prompt set for the play → report → fix loop with a coding agent: session rules, bug and feel report templates, and a verify step, so every round is one small diff checked against one number.
A fill-in prompt that gets an AI coding model to write a modern Three.js skeleton: ES modules, correct colour management, PMREM lighting, a damped camera rig, a shared loading manager, resize handling, a DPR cap and a perf HUD.
Write a one-page spec (core loop, controls, win and lose, camera, scope limits, acceptance tests) before you prompt, then build in small milestones you verify by playing. What goes in the spec, how big a step should be, and when to restart.
Tesana says a user built this fly-to-any-planet game from one prompt plus an image reference. We look at what that single prompt has to carry, and what it can't.
