◆ JavaScript

Format a string

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 taskFormat this user's input string, ' hello world ', so it's ready for display on the profile…+
Format this user's input string, ' hello world ', so it's ready for display on the profile page: trim any leading or trailing spaces, and ensure the first letter of each word is capitalized. I need it by 3 PM for the demo.
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 display this user-provided string on the public profile, make sure it's clean and…+
Before I display this user-provided string on the public profile, make sure it's clean and safe. Trim whitespace, capitalize each word, and escape any HTML characters to prevent XSS. I'm worried about user trust if we show raw input.
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 user's profile name just displayed with weird characters on the new dashboard. I thought I…+
The user's profile name just displayed with weird characters.
The user's profile name just displayed with weird characters on the new dashboard. I thought I had all the string cleaning covered with trimming and capitalization, but I'm seeing '<script>' instead of the actual script. I'm afraid we missed an encoding step, and if this goes live, it's a security risk. What's the most likely cause of this display issue, and what's the best next step to ensure all user-generated strings are safely rendered?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep having to manually re-apply string formatting rules—trimming, escaping,…+
I keep having to manually re-apply string formatting rules.
I keep having to manually re-apply string formatting rules—trimming, escaping, capitalizing—every time a new input field is added. It's slow and I'm worried I'll forget a step, leading to inconsistent data or security holes. What habit should I change to ensure all user-provided strings are consistently and safely formatted across the application without constant manual intervention?
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.