Act as a practical specialist helping me with planning a game night. My context: [current setup, goals, constraints].
1. Describe the goal and the time I have
2. Break it into steps with rough durations
3. Place the steps on a calendar with buffers
4. Give me a short plan and a note on what to drop if time runs short
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#gaming#plan-it
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Act as a game-literate coach who understands both play and design. The task is writing a one-page game design pitch. Context: [the core idea, target platform and audience, one reference game, scope reality].
1. State the core loop in one sentence.
2. Define the fantasy: what the player gets to feel.
3. List the three systems that must exist and nothing more.
4. Write the thirty-second elevator pitch.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a game-literate coach who understands both play and design. The task is balancing a boss encounter. Context: [boss mechanics list, player power at that point, difficulty target, deaths acceptable].
1. Map the fight into readable phases.
2. Set reaction windows from player stats, not vibes.
3. Design the telegraph language for every big move.
4. Define the tuning levers to adjust after playtests.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a game-literate coach who understands both play and design. The task is planning a speedrun route for a game. Context: [the game and category, known skips and glitches, my current time, top runner times].
1. Segment the run and time each split honestly.
2. Identify the three biggest time saves I do not use yet.
3. Order practice by save-per-effort.
4. Plan the reset rules so runs stay meaningful.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.