linting-neostandard-eslint9

Overview of linting-neostandard-eslint9 skill

linting-neostandard-eslint9 is a practical setup and migration skill for ESLint v9 flat config with neostandard. Use the linting-neostandard-eslint9 skill when you need a Standard-like baseline for JavaScript or TypeScript, want to move off legacy .eslintrc*, or need a clean eslint.config.js / eslint.config.mjs path that actually runs through eslint.

This skill is best for developers who want to get from “linting is broken or outdated” to a working, maintainable config with fewer compatibility guesses. It is especially useful for projects that are changing lint tooling, adding TypeScript, or standardizing CI and editor behavior.

What this skill is for

The main job of linting-neostandard-eslint9 is to help you choose and wire up the right flat-config baseline, not to invent a custom lint policy from scratch. It gives you a modern setup path for eslint@9, neostandard, and repo-level overrides that fit real projects.

When it fits best

Use it if you are:

• starting a new JS or TS repo with ESLint v9
• migrating from standard to neostandard
• replacing legacy ESLint RC config with flat config
• aligning local linting, CI, and pre-commit hooks
• debugging why a flat config or rule combination behaves unexpectedly

What matters most

The differentiator is that neostandard is treated as a shared ESLint flat config, not a separate linter. That means the skill centers on the actual execution path: install eslint, generate or author eslint.config.*, then run eslint .. That distinction matters because many adoption problems come from assuming neostandard is the command being run.

How to Use linting-neostandard-eslint9 skill

Install and confirm the execution model

Use the linting-neostandard-eslint9 install flow when your repo needs a clean ESLint v9 baseline:

npm install --save-dev eslint neostandard

Then make sure your workflow runs ESLint, not a legacy wrapper:

npx eslint .

If you are starting from a blank slate, create eslint.config.js or eslint.config.mjs and keep the config root-level and simple before adding overrides.

Turn your goal into a useful prompt

The linting-neostandard-eslint9 usage works best when you provide the agent with concrete constraints, not just “set up linting.” Good input includes:

• package manager: npm, pnpm, yarn, or bun
• language mix: JS only, TS only, or both
• config preference: eslint.config.js or eslint.config.mjs
• migration source: .eslintrc, standard, or no existing linting
• editor/CI needs: VS Code, GitHub Actions, pre-commit, or all three

Stronger prompt example:
“Set up linting-neostandard-eslint9 for a TypeScript monorepo using pnpm. We currently use .eslintrc, want flat config, need CI lint only, and want VS Code save fixes.”

Read the right files first

For this skill, the fastest path is:

1. SKILL.md for the core setup model
2. rules/eslint-v9-flat-config.md for flat-config structure
3. rules/neostandard.md for options and execution details
4. rules/migration-from-legacy-eslint.md or rules/migration-from-standard.md if you are converting an existing repo
5. rules/ci-and-editor-integration.md if you need automation or editor behavior

Those files show where the skill is opinionated and where you should adapt it to your project.

Apply it in a real repo workflow

A reliable linting-neostandard-eslint9 guide sequence is:

• install dependencies
• generate or write eslint.config.*
• run npx eslint .
• fix rule parity issues before adding CI enforcement
• add lint and lint:fix scripts
• only then wire pre-commit or editor auto-fix

If you are migrating, keep the config change small first. Validate parity before you introduce unrelated formatter, test, or CI changes.

linting-neostandard-eslint9 skill FAQ

Is linting-neostandard-eslint9 only for new projects?

No. It is often more valuable for existing repos because migration is where most adoption friction happens. The skill is a good fit if you are moving from standard, legacy ESLint RC files, or a mixed setup that no longer matches ESLint v9.

Do I need neostandard if I already know ESLint?

Not necessarily, but neostandard reduces decision work if you want a Standard-like default on top of ESLint v9 flat config. If you need highly custom rules, a manual flat config may be better than this skill’s baseline path.

Is this better than writing a quick prompt to an AI editor?

Usually yes, when you care about correctness and repeatability. The linting-neostandard-eslint9 skill gives a known install and config path, plus migration guidance and integration details. A generic prompt often misses the eslint vs neostandard execution model, flat-config structure, or CI/editor boundaries.

When should I not use this skill?

Skip it if your project is:

• committed to a non-ESLint lint stack
• using a highly custom corporate lint standard that does not resemble neostandard
• already stable on flat config with no migration need
• relying on formatter-first workflows where lint rules are intentionally minimal

How to Improve linting-neostandard-eslint9 skill

Give the skill the exact repo shape

The biggest quality gain comes from specifying what files exist and what must be linted. Tell it whether you need *.js, *.mjs, *.cjs, *.ts, *.mts, or *.cts, and whether tests, scripts, or config files should be included. That avoids overbroad or incomplete files and ignores choices.

State your constraint tradeoffs up front

The most useful linting-neostandard-eslint9 skill outputs usually come from clear priorities:

• “prefer minimal config”
• “keep semicolons off”
• “avoid style rules because Prettier handles formatting”
• “support TypeScript imports correctly”
• “do not add rules that break existing CI immediately”

Those constraints help the skill choose between baseline neostandard defaults, ts: true, semicolon mode, and targeted overrides.

Watch for the common failure modes

The main mistakes are mixing legacy and flat config, assuming neostandard is the command to run, and adding TS rules without disabling conflicting base JS rules. Another common problem is trying to migrate config, CI, and rule semantics all at once. Change one layer, verify it, then move on.

Iterate from the first lint run

Use the first npx eslint . output as feedback, not as a final verdict. If the result is too noisy, share the exact errors and the current eslint.config.*; if it is too permissive, list the rules or file types you expected to be covered. For better second-pass help, include the current config, the failing paths, and whether the repo should behave like Standard or like a custom ESLint policy.