◆ JavaScript

Conduct playtesting and iterate designs

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

3prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AImprove — make it easier to acceptBefore we start our next playtesting session for the new tutorial flow, help me design a…+
Before we start our next playtesting session for the new tutorial flow, help me design a JavaScript object to capture player feedback. It needs to include fields for `playerId`, `sessionDuration`, `completionStatus`, and `bugReports` (an array of strings). Also, suggest a simple way to store this data locally in the browser between sessions so we don't lose anything if the player closes the tab prematurely.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentThe latest playtest results show players are consistently abandoning the game at the same…+
The latest playtest results show players are consistently abandoning the game at the same puzzle, but I don't know why.
The latest playtest results show players are consistently abandoning the game at the same puzzle, but I don't know why. The analytics show a sharp drop-off, but no specific error messages. I'm afraid the puzzle is either too hard, poorly explained, or has a subtle bug I haven't caught. The design lead is expecting concrete reasons and solutions by end of day. I can't just say 'players quit.' What's the most effective way to diagnose the root cause of this player abandonment, and what's the best immediate action I can take to gather more specific insights from the next round of testers?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CBecome — change the patternI keep pushing design iterations based on gut feelings, only to find out later they don't solve…+
I keep pushing design iterations based on gut feelings, only to find out later they don't solve the core player issues.
I keep pushing design iterations based on gut feelings, only to find out later they don't solve the core player issues, leading to wasted development time and frustrated players. It feels like I'm not truly understanding the player experience despite all the playtesting data. What habit should I change in how I analyze playtest feedback and translate it into actionable design changes to ensure I'm addressing the right problems effectively?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.