◆ HTML

Archive data manually

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 taskArchive the current content of the 'Q3 Marketing Campaign' landing page. Save it as a static…+
Archive the current content of the 'Q3 Marketing Campaign' landing page. Save it as a static webpage file in the 'Archived Campaigns/2023' folder by end of day.
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 deprecate the 'Q3 Marketing Campaign' landing page, create a complete, self-contained…+
Before we deprecate the 'Q3 Marketing Campaign' landing page, create a complete, self-contained archive of its webpage content, CSS, and JavaScript. Ensure all relative paths are updated to work locally, and embed any critical assets, so it's fully viewable offline for future reference and compliance audits.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentLegal just requested an exact, verifiable copy of the 'Summer Sale 2022' campaign landing page…+
Legal just asked for a copy of a specific page from last year's campaign, and I can't find a complete version.
Legal just requested an exact, verifiable copy of the 'Summer Sale 2022' campaign landing page for an audit, and I can only find fragments of its webpage content. I'm afraid we don't have a complete, functional archive. What's the likely reason our past archiving efforts have been incomplete, and what's the best next step to reconstruct or verify that page for legal?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently waste valuable time trying to reconstruct or verify old web pages for…+
I waste too much time trying to reconstruct old web pages for compliance or historical review.
I consistently waste valuable time trying to reconstruct or verify old web pages for compliance, legal audits, or historical review because our archives are often incomplete or broken. This creates unnecessary stress and risk. What habit should I change in how I approach archiving web content to ensure every page can be fully and reliably retrieved later?
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 HTML'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.