◆ HTML

Interface web applications with enterprise systems

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 HTML tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGet the new inventory data from the SAP export into the customer-facing order system. Make sure…+
Get the new inventory data from the SAP export into the customer-facing order system. Make sure all the product IDs match and the quantity updates correctly by Friday morning, so the sales team can see accurate stock levels.
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 push this inventory update live, check if any of the new product descriptions are too…+
Before I push this inventory update live, check if any of the new product descriptions are too long for the mobile view, or if any of the pricing fields are showing more than two decimal places. It needs to look clean for customers on their phones.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new product feed from the supplier just came in, and the SKU numbers don't align with our…+
The new product feed from the supplier has a different structure than our system expects.
The new product feed from the supplier just came in, and the SKU numbers don't align with our internal database, and some fields are missing. If I force it through, we'll have mismatched products and wrong prices on the site, which will be a huge headache for customer service. What's the fastest way to map these new fields without breaking existing product pages, and should I flag this with the procurement lead first?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly burning time manually mapping fields every time a new data source comes in or an…+
I keep spending hours manually mapping fields between our internal systems and external data feeds.
I'm constantly burning time manually mapping fields every time a new data source comes in or an existing one changes. This is killing my sprint velocity. What habit can I change to build more resilient, adaptable data ingestion processes that don't require me to be a human translator every other week?
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.