◆ JavaScript

Set up linter rules

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
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWe have a release branch ready. Apply the linter rules to the codebase, auto-fix style issues…+
We have a release branch ready. Apply the linter rules to the codebase, auto-fix style issues where safe, and produce a list of remaining errors that require manual judgment. Use the team’s agreed ECMAScript style, enforce no-console in production files, and fail if any rule marked critical is violated.
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 push lint rules to the whole team, make them easy to accept. Surface which rules will…+
Before I push lint rules to the whole team, make them easy to accept. Surface which rules will cause most churn, show examples of current code that will break the build, recommend a gradual rollout plan (auto-fix then enforce), and flag rules that affect runtime semantics versus pure style so reviewers know what to care about.
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 flipped the new lint rules on and CI started failing for half the team with about 200 new…+
CI is now failing for many developers after lint enforcement
I flipped the new lint rules on and CI started failing for half the team with about 200 new errors. I wanted to enforce quality but not block work. I don’t know which errors are urgent and which can wait. What subset of rules should I relax or defer immediately to unblock developers while keeping the most important guarantees intact?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep tightening linter rules and every few months it causes a sprint of reworks, which kills…+
Lint rule churn frustrates the team
We keep tightening linter rules and every few months it causes a sprint of reworks, which kills morale. The team either disables rules or ignores them. What rules-management habit or rollout process will stop the churn, keep code quality improving, and avoid demoralizing sudden breakages?
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.