◆ HTML

Adapt software to another language

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 taskTranslate the 'About Us' page content into Spanish and replace the existing English text on the…+
Translate the 'About Us' page content into Spanish and replace the existing English text on the Spanish version of the site. Get it done 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 acceptWhen I adapt our main product page for the Japanese market, I need to ensure the layout…+
When I adapt our main product page for the Japanese market, I need to ensure the layout accommodates longer text without breaking, and that any culturally specific images are swapped out. It needs to feel local and natural for a Japanese customer.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe just launched our German site, and the marketing team is saying some of the translated…+
We just launched our German site, and the marketing team is saying some of the translated call-to-action buttons are too long.
We just launched our German site, and the marketing team is saying some of the translated call-to-action buttons are too long, breaking the layout on mobile. I'm afraid this will hurt conversion rates. I can't tell if it's a simple CSS fix or if we need to shorten the German phrases themselves. What's the best immediate action to take to fix this without needing a full re-translation?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself adjusting layouts and truncating text after content has been translated…+
I often find myself adjusting layouts and truncating text after content has been translated into different languages.
I often find myself adjusting layouts and truncating text after content has been translated into different languages because it doesn't fit the original design. It's a constant reactive effort. What habit can I change in the initial design or content preparation phase to better anticipate and accommodate the varying lengths and structures of different languages?
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.