◆ MATLAB

Add a file to MATLAB directory

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 taskCopy the 'experimental_data.csv' file from my Downloads folder into the current project…+
Copy the 'experimental_data.csv' file from my Downloads folder into the current project directory so my script can find it.
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 send this data analysis script to Dr. Chen, make sure all the input data files are…+
Before I send this data analysis script to Dr. Chen, make sure all the input data files are properly organized within the project folder. Can you also check if any of the data files are unusually large and might cause issues for his system, and let me know which ones to compress?
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 ran my 'analyze_sensor_readings.m' script, and the results are based on old data, even though…+
My script isn't loading the latest sensor data, even though I just updated the file in the project folder.
I ran my 'analyze_sensor_readings.m' script, and the results are based on old data, even though I copied the new 'sensor_log_0515.txt' into the project folder just five minutes ago. I'm afraid I'll present outdated findings to the team meeting in an hour. Is there a file caching issue, or am I accidentally loading from a different location? What's the most reliable way to ensure the script always sees the absolute latest version of the input file?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm always losing time because my scripts can't locate data files or other dependencies,…+
I waste too much time tracking down files that my scripts can't find.
I'm always losing time because my scripts can't locate data files or other dependencies, leading to broken analyses and missed deadlines. This happens even when I think I've put everything in the right place. How can I develop a more robust habit for managing project files and their paths that prevents these constant interruptions and ensures my code runs smoothly every time?
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 MATLAB'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.