◆ JavaScript

Format dates and times

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe dashboard shows timestamps as raw ISO strings. Convert the createdAt and updatedAt fields…+
The dashboard shows timestamps as raw ISO strings. Convert the createdAt and updatedAt fields to user-local format: show date as MMM DD, YYYY and time as HH:mm in the user's locale, updating when the timezone changes. Make sure this runs on page load and when the user switches accounts, ready for Monday's demo.
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 ship this to the UX lead, make the date formatting easy to review: put the format…+
Before I ship this to the UX lead, make the date formatting easy to review: put the format function next to the display component, show an example input and output at the top, and flag any places that still call toString on the Date object or assume UTC.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers in CET see times shifted by several hours after daylight saving; I used fixed timezone…+
times show wrong timezone for some users
Users in CET see times shifted by several hours after daylight saving; I used fixed timezone offsets when formatting timestamps for the activity feed. I can't reproduce locally because my machine is in PST. What's likely causing the DST shift and the safest fix to ensure dates render correctly across timezones without requiring server changes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep wasting cycles because each component formats dates differently, introducing layout…+
formatting logic duplicated and brittle
We keep wasting cycles because each component formats dates differently, introducing layout shifts and timezone bugs. Which habit should we change to reduce bugs: where to centralize formatting, a small API for relative vs absolute time, and one test to prevent regressions?
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.