◆ MATLAB

Develop a MATLAB BMS model

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 taskTake the BMS model I've been working on, the one for the new EV battery pack, and develop it so…+
Take the BMS model I've been working on, the one for the new EV battery pack, and develop it so it accurately reflects the cell balancing logic we discussed for the 48V system. Make sure the over-current protection trips at 150A. I need this by Wednesday for the review with the lead engineer.
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 hand off this BMS model to the test team, make it robust and easy for them to…+
Before I hand off this BMS model to the test team, make it robust and easy for them to validate. Can you add clear comments for each major block, ensure all critical parameters are easily adjustable from a top-level script, and flag any areas that might cause numerical instability during long simulations?
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've integrated the latest sensor data into the BMS model, but the cell temperatures are…+
The new cell temperature sensor data is spiking unexpectedly, and I can't tell if it's a sensor fault or a real thermal runaway condition in the model.
I've integrated the latest sensor data into the BMS model, but the cell temperatures are showing erratic spikes, far beyond what's physically plausible. I'm afraid to continue testing without understanding if this is a data issue, a model error in the thermal dynamics, or a genuine runaway scenario I'm missing. What's the most likely diagnosis, and what's the quickest way to isolate the root cause before Friday's safety 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 frequently find myself spending hours debugging unexpected side effects in the BMS model…+
I keep losing time debugging complex interactions between different BMS sub-systems after making seemingly small changes.
I frequently find myself spending hours debugging unexpected side effects in the BMS model after making minor adjustments to a single sub-system, like the state-of-charge estimator or cell balancing. This eats into my design time and delays integration. What habit should I change to better anticipate these interactions and build more modular, less interdependent model components from the start?
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.