◆ JavaScript

Assign multiline string literal

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskAssign this block of text to a variable named 'welcomeMessage'. It's a standard greeting for…+
Assign this block of text to a variable named 'welcomeMessage'. It's a standard greeting for new users and needs to be ready for the Tuesday morning release.
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 put this into the 'about' section of the website, assign this multi-line block of text…+
Before I put this into the 'about' section of the website, assign this multi-line block of text to a constant. Make sure it preserves all line breaks and special characters exactly as written, so it renders perfectly on the page. We want our brand voice to be consistent.
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 description just displayed with all the line breaks removed, making it one…+
The new product description just displayed with all the line breaks removed, making it unreadable.
The new product description just displayed with all the line breaks removed, making it one long, unreadable paragraph. I assigned it as a multi-line string, but clearly something went wrong during rendering. I'm afraid customers won't understand the features, and sales will suffer. What's the most likely reason the line breaks were lost, and what's the best next step to ensure the text displays exactly as I wrote it, preserving all formatting?
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 struggle with correctly embedding long blocks of text—like legal disclaimers or…+
I frequently struggle with correctly embedding long blocks of text.
I frequently struggle with correctly embedding long blocks of text—like legal disclaimers or marketing copy—into the application. I lose formatting, or special characters break. It wastes my time fixing small display issues. What habit should I change to reliably handle multi-line strings with special characters, ensuring they render perfectly every time without manual tweaking?
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 JavaScript'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.