◆ JavaScript

Get screen or window size

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 make sure the image gallery displays correctly on Mary's new ultrawide monitor. Get…+
I need to make sure the image gallery displays correctly on Mary's new ultrawide monitor. Get the current width and height of the browser window so I can adjust the layout.
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 we launch the new responsive layout for the product page, check how much horizontal…+
Before we launch the new responsive layout for the product page, check how much horizontal space is actually available for the main content area. We need to ensure the critical 'buy now' button is always visible and not pushed off-screen, no matter the device.
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 new modal for adding items to the cart is causing scrollbars on some smaller laptops, and…+
The new modal for adding items to the cart is causing scrollbars on some smaller laptops, and users are complaining.
The new modal for adding items to the cart is causing scrollbars on some smaller laptops, and users are complaining. I thought I tested it thoroughly, but I clearly missed something. I'm afraid of a bad user experience during the holiday rush. I can't just guess at the right size. What's the best way to reliably get the actual viewport dimensions to dynamically resize the modal and avoid scrollbars, and how can I quickly test this across common screen sizes before Friday's deployment?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternLayout issues on various screen sizes always surface late in the development cycle, leading to…+
Layout issues on various screen sizes always surface late in the development cycle, leading to frantic last-minute fixes.
Layout issues on various screen sizes always surface late in the development cycle, leading to frantic last-minute fixes. This is burning me out and affecting our release schedule. What habit should I change to proactively account for different screen or window sizes earlier, so we catch these problems before they become emergencies?
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.