◆ JavaScript

Archive application data

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 taskArchive all customer interaction logs for accounts that have been inactive for more than two…+
Archive all customer interaction logs for accounts that have been inactive for more than two years into the designated long-term storage bucket.
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 we archive the Q2 2022 transaction data, ensure that all associated metadata, like…+
Before we archive the Q2 2022 transaction data, ensure that all associated metadata, like customer IDs and payment methods, are properly indexed and tagged. This will make future audits by the compliance team much faster and prevent us from having to dig through raw files later.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur legal team just requested all data for a specific customer from five years ago for a new…+
Our legal team just requested all data for a specific customer from five years ago, and I can't locate it in our standard archives.
Our legal team just requested all data for a specific customer from five years ago for a new case, and I can't locate it in our standard archives. I'm afraid of non-compliance fines and delaying the legal process. I don't know if it was archived incorrectly, deleted, or stored in an unexpected location. What's the most likely diagnosis, and what's the best next move to find this critical data before Friday's deadline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI constantly struggle to retrieve specific historical data when legal or compliance asks for…+
I constantly struggle to retrieve specific historical data when legal or compliance asks for it.
I constantly struggle to retrieve specific historical data when legal or compliance asks for it, leading to frantic searches and missed deadlines. This makes me doubt our entire data retention strategy. What habit should I change in how we categorize and store archived data to ensure I can quickly and accurately find what's needed for future requests?
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.