◆ HTML

Generate HTML reports

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 taskGenerate a report for last month's sales figures. It needs to display the total revenue, top 5…+
Generate a report for last month's sales figures. It needs to display the total revenue, top 5 products, and regional breakdown. The data is in the database export.
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 send this sales report to the executive team, make it easier for them to quickly grasp…+
Before I send this sales report to the executive team, make it easier for them to quickly grasp the key insights. Emphasize the growth areas, make the charts more prominent, and ensure the summary is at the very top. They don't have time to dig for information.
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'm creating the sales report for last quarter, and the West region shows a significant…+
I'm creating the HTML sales report, but I'm unsure how to present the negative growth in the West region without alarming the CEO.
I'm creating the sales report for last quarter, and the West region shows a significant negative growth. I'm afraid of presenting this raw data to the CEO without context, as it could lead to an immediate panic. How can I structure the report to clearly show the data, but also include a brief, mitigating explanation or highlight other positive areas, without looking like I'm hiding anything?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy reports often lack clarity, leading to endless follow-up questions from stakeholders like…+
My HTML reports often lack clarity and lead to follow-up questions from stakeholders.
My reports often lack clarity, leading to endless follow-up questions from stakeholders like the marketing director, who needs specific numbers for her campaigns. I find myself constantly explaining what the data means. What habit should I change to build more self-explanatory reports, ensuring that the key takeaways and supporting details are immediately obvious and actionable, reducing the need for constant clarification?
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.