◆ JavaScript

Design web-based learning aids

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 taskBuild a simple web page that displays a list of array methods, with a brief description and…+
Build a simple web page that displays a list of array methods, with a brief description and example for each. Make sure it's responsive for mobile viewing.
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 present this to the junior devs for their onboarding, make the learning aid more…+
Before I present this to the junior devs for their onboarding, make the learning aid more interactive. Add a small code editor for each example that lets them run and modify the code directly, and include a 'reset' button.
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 interactive learning aid I built for the new hires is failing on Safari 14 and IE11, but…+
The new interactive learning aid is buggy on older browsers.
The interactive learning aid I built for the new hires is failing on Safari 14 and IE11, but works fine on Chrome and Firefox. I'm afraid if it's not consistent, it'll confuse them and make their first week harder. I can't tell the team lead it's broken, not after I promised it would be ready. What's the most likely cause for this browser incompatibility, and what's the fastest way to get it working across all target browsers before Monday?
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 building features using modern JavaScript syntax or APIs, only to find them breaking on…+
I keep building features that break on older browsers.
I keep building features using modern JavaScript syntax or APIs, only to find them breaking on older browsers that our users still rely on. This always leads to last-minute scrambles and hotfixes. What habit should I change to consistently ensure broader browser compatibility without always needing a polyfill library?
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.