◆ JavaScript

Predict physical system outcomes

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 taskRun the simulation for the new motor's thermal profile using the latest material parameters and…+
Run the simulation for the new motor's thermal profile using the latest material parameters and output the maximum temperature at 100% load for 30 minutes. Make sure the results are saved to the project's 'Motor_V3_Thermal' folder.
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 these motor thermal simulation results to the mechanical team, highlight any…+
Before I present these motor thermal simulation results to the mechanical team, highlight any areas that exceed 85 degrees Celsius and suggest design changes to improve heat dissipation, making it clear why those areas are critical.
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 thermal simulation for the motor's new housing just finished, but the temperature curve is…+
The last simulation run for the new motor showed unexpected oscillations in the temperature curve.
The thermal simulation for the motor's new housing just finished, but the temperature curve is oscillating wildly after the first 10 minutes, which I've never seen before with these materials. I'm afraid I've got a fundamental model error or a bad input parameter, and I can't tell if it's the material properties or the boundary conditions. What's the most likely cause, and what's the quickest way to isolate it before I miss the Friday design review?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI repeatedly find myself debugging unexpected simulation outputs just before critical reviews,…+
I keep getting caught off guard by unexpected behaviors in physical system simulations.
I repeatedly find myself debugging unexpected simulation outputs just before critical reviews, losing hours trying to pinpoint the root cause in complex physical models. I need a better way to proactively identify potential instabilities or parameter sensitivities before running full simulations. What habit should I change to catch these issues earlier in my workflow?
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.