◆ JavaScript

Create a component

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 taskI need a reusable card component that shows a title, an image, and a short description for the…+
I need a reusable card component that shows a title, an image, and a short description for the product list. Build it as a function that returns a DOM element, accepts data with keys title, imgSrc, and summary, and applies accessible attributes so screen readers announce the title. Make the component create elements rather than injecting innerHTML so it is safe for untrusted data.
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 share this component with the team, make it easier to drop into existing pages: expose…+
Before I share this component with the team, make it easier to drop into existing pages: expose a simple API that accepts a plain object for title, imgSrc, summary and a mount target element. Add notes about which parts should be styled externally and flag any attributes or classes that will interfere with global CSS resets.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI built a card component that returns a DOM tree for product pages, but CI intermittently fails…+
The new card renders but images sometimes don't load in CI tests.
I built a card component that returns a DOM tree for product pages, but CI intermittently fails because images 404 or slow-load. The stakeholders are content editors and the QA lead. I can't tell if I should add lazy loading, placeholder SVGs, or change how I surface errors. What is the likely diagnosis and the single best change to make the component resilient in tests and previews?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross projects we keep creating near-duplicate card components with small prop differences.…+
Every page has slightly different micro-components for similar cards.
Across projects we keep creating near-duplicate card components with small prop differences. This costs review time and confuses style updates. Where do we lose time and authority, and what habit should we adopt to stop proliferating one-off components while keeping designers happy?
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.