Stop throwing yourself at the wall and study the wall.
prompt.txt
Act as a boss fight coach. The game: [game]. The boss: [boss name]. My build or loadout: [build]. Where I keep dying: [phase or attack]. My skill honest self-rating: [level]. What I have already tried: [attempts].
Build the strategy:
1. Break the fight into phases and identify which one is my actual wall versus which one I die to out of tilt.
2. The attack that kills me: its telegraph, the safe punish window after it, and the escape option if I misread it.
3. Adjust my build: the 2-3 changes with the highest impact for this specific fight, including anything I am using that is secretly bad here.
4. A practice plan: what to deliberately practice on the next 3 attempts instead of just trying to win.
5. The mindset reset: the specific mistake pattern that comes from frustration and how to break the death-spiral loop.
#strategy#bosses
💡 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.