◆ JavaScript

Create a GUID or UUID

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.

4prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGenerate a new unique identifier for this new user record. I need it for the `id` field in the…+
Generate a new unique identifier for this new user record. I need it for the `id` field in the database.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I save this new `session` object, generate a globally unique identifier for it. This…+
Before I save this new `session` object, generate a globally unique identifier for it. This will ensure that every user session has a distinct ID across all our servers.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new `order` is being created, and it requires a unique ID that can be reliably used across…+
I need to generate a unique ID for a new `order` that will be processed across multiple microservices, and I'm concerned about potential collisions or performance bottlenecks if I don't choose the right method.
A new `order` is being created, and it requires a unique ID that can be reliably used across our distributed system. I'm afraid of generating duplicate IDs or introducing a performance hit if the generation method isn't robust. What's the most appropriate way to generate a globally unique identifier in this context, and what's the best next move to implement it without issues?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm frequently generating unique IDs for different types of data, and I find myself sometimes…+
I often need to generate unique identifiers for various entities (users, orders, sessions), and I'm not consistently using the most appropriate or secure method.
I'm frequently generating unique IDs for different types of data, and I find myself sometimes using simple counters, sometimes random strings, and sometimes more robust methods. This inconsistency makes me worry about collisions or security vulnerabilities. What habit should I change to ensure I always select and implement the most suitable and secure unique identifier generation strategy, so I stop second-guessing myself?
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.