◆ JavaScript

Store data in localStorage

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 taskI need this page to remember the user's draft between visits. Save the current form object as…+
I need this page to remember the user's draft between visits. Save the current form object as JSON under key draftProfile in localStorage whenever the user blurs a field or clicks Save. Before writing, read draftProfile, merge incoming values so we don't wipe unset fields, and only write if something actually changed. On write, also set lastSavedDraft to an ISO timestamp for audit.
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 wire this up to the client's browser, make the draft easy to recover and inspect.…+
Before I wire this up to the client's browser, make the draft easy to recover and inspect. Surface a clear message when a draft exists, show the lastSavedDraft timestamp at the top, and put a Recover draft button that loads values without overwriting anything the user has changed in the current session. Flag fields that are missing from the draft versus the form schema so a reviewer doesn't think data silently disappeared.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI closed the settings tab after entering about half the profile. I reopened and the form is…+
User closed the tab and swore their half-filled form would exist next time
I closed the settings tab after entering about half the profile. I reopened and the form is empty. I checked localStorage and found draftProfile present but not populating the form. Priya on support will blame our save logic. What's the likely cause — JSON mismatch, key name typo, or merge strategy — and what's the smallest fix I should try first to restore drafts without losing users' current input?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several sprints we keep getting bug reports: users lose partially completed forms or see…+
We repeatedly lose people’s unsaved inputs between sessions
Across several sprints we keep getting bug reports: users lose partially completed forms or see stale drafts. Each fix is a quick patch and the problem returns. Which habit should we change to stop this cycle? Propose a single checklist item and one small architectural change that would prevent accidental overwrite and make recovery reliable.
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.