◆ JavaScript

Check if element is hidden

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 taskI need to confirm the 'submit order' button isn't visible on the checkout page when the cart is…+
I need to confirm the 'submit order' button isn't visible on the checkout page when the cart is empty before we push this update live. Can you check that for me?
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 build to QA, make sure the 'add to cart' button is only shown when the…+
Before I send this build to QA, make sure the 'add to cart' button is only shown when the product is in stock. If it's out of stock, hide the button to avoid user frustration and support tickets.
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 client just reported that users can still click the 'checkout' button even after they've…+
The client just reported that users can still click the 'checkout' button even after they've removed all items from their cart.
The client just reported that users can still click the 'checkout' button even after they've removed all items from their cart, leading to an empty order. I'm worried about the user experience and potential data issues. What's the most robust way to ensure that button is absolutely hidden and unclickable if the cart is empty, without impacting performance for other users?
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 getting bug reports about interactive elements showing up when they shouldn't, or being…+
I keep getting bug reports about interactive elements showing up when they shouldn't, or being hidden when they should be visible.
I keep getting bug reports about interactive elements showing up when they shouldn't, or being hidden when they should be visible. This leads to frustrating user experiences and extra QA cycles. What habit should I change to ensure I consistently manage element visibility more reliably across different states and user roles?
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.