◆ HTML

Manage HTML projects within scope and budget

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 taskI need to update the copyright year in the footer of the main company website to 2024. This is…+
I need to update the copyright year in the footer of the main company website to 2024. This is a quick change, just find the existing year and update it.
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 next sprint planning, I need a quick estimate for adding a new 'News' section to the…+
Before the next sprint planning, I need a quick estimate for adding a new 'News' section to the existing homepage. It should display the three most recent articles with a title, a short blurb, and a 'Read More' link. Consider existing styles but don't worry about the content yet.
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 director just requested a major redesign of the product landing page, including…+
The marketing director just requested a major redesign of the product landing page, but the project budget is almost depleted.
The marketing director just requested a major redesign of the product landing page, including new interactive elements and a carousel, citing competitive pressure. The project budget is almost depleted, and our current developer time is fully allocated to other high-priority tasks for the next two weeks. I can't tell her no, but I'm afraid of burning out the team or going over budget again. What's the best next move to address this without causing a crisis?
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 underestimate the time required for seemingly small structural changes, leading to…+
I frequently underestimate the time required for seemingly small HTML changes, leading to missed internal deadlines.
I frequently underestimate the time required for seemingly small structural changes, leading to missed internal deadlines and pressure from the project manager. It's often due to unexpected browser compatibility issues or subtle CSS conflicts. What habit should I change in my estimation process to account for these hidden complexities and provide more accurate timelines for structural tasks?
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.