◆ HTML

Move an element into another element

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 taskMove the 'Add to Cart' button from the bottom of the product description up into the product…+
Move the 'Add to Cart' button from the bottom of the product description up into the product image gallery container. It needs to be more prominent 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 the A/B test goes live, move the 'Request Demo' button on the landing page into the hero…+
Before the A/B test goes live, move the 'Request Demo' button on the landing page into the hero section, right below the main headline. We want to see if placing it higher on the page improves conversion rates. Ensure it maintains its styling and responsiveness.
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 marketing team just asked to move the newsletter signup form from the footer to a modal…+
The marketing team wants to move the signup form, but I'm worried about breaking its functionality.
The marketing team just asked to move the newsletter signup form from the footer to a modal popup that appears after 30 seconds on the homepage. I'm worried about breaking the form's submission logic or its integration with the CRM if I just cut and paste. The marketing director is pushing for this change by Friday. What's the safest way to move this complex element without introducing new bugs or losing existing functionality?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently break styling or functionality when I have to move complex elements, like forms or…+
I often break styling or functionality when moving complex elements around the page.
I frequently break styling or functionality when I have to move complex elements, like forms or interactive widgets, to a different part of the page. This leads to unexpected bugs and delays, especially when under pressure from marketing. What habit can I change to better anticipate and manage the dependencies and side effects when relocating significant page components?
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.