Login
mcollina/skills7 files

Linting Neostandard Eslint9

Configures ESLint v9 flat config and neostandard for JavaScript and TypeScript projects, including migrating from legacy `.eslintrc*` files or the `standard` package. Use when you need to set up or fix linting with `eslint.config.js` or `eslint.config.mjs`, troubleshoot lint errors, configure neostandard rules, migrate from `.eslintrc` to flat config, or integrate linting into CI pipelines and pre-commit hooks.

Use this skillView repositoryView on skills.sh
Specification
Skill ID
mcollina/skills/linting-neostandard-eslint9
Publisher
mcollina
Repository
skills
Installs
0
Files
7
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

mcollina/skills/linting-neostandard-eslint9Installs these files
  • SKILL.md
  • rules/ci-and-editor-integration.md
  • rules/eslint-v9-flat-config.md
  • rules/migration-from-legacy-eslint.md
  • rules/migration-from-standard.md
  • rules/neostandard.md
  • tile.json

What this skill tells the agent

When to use

Use this skill when you need to:

  • Set up linting in a JavaScript or TypeScript project
  • Use neostandard as a Standard-like ESLint v9 flat-config baseline
  • Configure eslint@9 with the flat config system (eslint.config.js/eslint.config.mjs)
  • Migrate from standard to neostandard or ESLint v9
  • Migrate from legacy .eslintrc* configuration to ESLint v9
  • Run linting consistently in CI and local development

Quick start: basic neostandard setup

Install dependencies and create a minimal eslint.config.js:

npm install --save-dev eslint@9 neostandard
// eslint.config.js
import neostandard from 'neostandard'

export default neostandard()

Verify the config works:

npx eslint .

Common setup workflow (new project)

  1. Install eslint@9 and neostandard (see Quick start above)
  2. Create eslint.config.js with neostandard() as the base
  3. Add any project-specific rule overrides on top
  4. Run npx eslint . to confirm no config errors
  5. Add a lint script to package.json: "lint": "eslint ."
  6. Integrate into CI with a non-fix run; use --fix only in local workflows

How to use

Read individual rule files for implementation details and examples:

  • rules/neostandard.md - Install, configure, and extend neostandard with ESLint
  • rules/eslint-v9-flat-config.md - Build ESLint v9 flat config for JS/TS projects
  • rules/migration-from-standard.md - Migrate from standard to neostandard or ESLint v9
  • rules/migration-from-legacy-eslint.md - Migrate from .eslintrc* to flat config safely
  • rules/ci-and-editor-integration.md - CI scripts, pre-commit, and editor setup

Core principles

  • Prefer reproducible linting with pinned major versions
  • Keep config minimal and explicit
  • Use flat config for ESLint v9 projects
  • Treat lint failures as quality gates in CI
  • Enable auto-fix for local workflows, but validate with non-fix CI runs

More from mcollina

mcollina/skills

Fastify Best Practices

Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication, configuring CORS and security headers, integrating databases, working with WebSockets, and deploying to production. Covers the full Fastify request lifecycle (hooks, serialization, logging with Pino) and TypeScript integration via strip types. Trigger terms: Fastify, Node.js server, REST API, API routes, backend framework, fastify.config, server.ts, app.ts.

mcollina/skills

Documentation

Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.

mcollina/skills

Init

Creates, updates, or optimizes an AGENTS.md file for a repository with minimal, high-signal instructions covering non-discoverable coding conventions, tooling quirks, workflow preferences, and project-specific rules that agents cannot infer from reading the codebase. Use when setting up agent instructions or Claude configuration for a new repository, when an existing AGENTS.md is too long, generic, or stale, when agents repeatedly make avoidable mistakes, or when repository workflows have changed and the agent configuration needs pruning. Applies a discoverability filter—omitting anything Claude can learn from README, code, config, or directory structure—and a quality gate to verify each line remains accurate and operationally significant.

Use this skill in a project

Open any RiverX project, search the Skills panel for mcollina/skills/linting-neostandard-eslint9, and install it in one click.

Use this skill