eslint

Creates ESLint 10 flat configs for JavaScript/TypeScript with Prettier coexistence.

15|2|Updated May 23, 2026
One-click install
npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill eslint-vkirill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eslint
Source: https://github.com/VKirill/antigravity-for-claude-code/tree/main/skills/eslint
Command: npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill eslint-vkirill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the confusion and breakage that happens when setting up ESLint 10 in modern JavaScript/TypeScript projects, especially when moving to flat config, enabling type-aware rules with typescript-eslint, and combining framework plugins with Prettier coexistence.

Core Features & Use Cases

  • Flat config (ESLint 10 only): Build eslint.config.js / eslint.config.ts using the v10-supported flat array shape and correct file scoping.
  • Type-aware typescript-eslint: Enable project service linting (projectService: true) to unlock more accurate rules and avoid common monorepo path issues.
  • Framework + tooling coexistence: Add React/Vue/Next/Nuxt/Astro/Storybook/jx-a11y linting and ensure style rules don’t conflict with Prettier (via eslint-config-prettier last).
  • Migration guidance: Move from legacy .eslintrc.* to flat config with the right order, plugin translation, and verification steps.

Quick Start

Ask the skill: “Create an eslint.config.ts for my TypeScript Next.js project using ESLint 10 with type-aware rules and framework plugins, and make sure Prettier coexistence is configured correctly.”

Frequently Asked Questions about eslint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up ESLint 10 flat config for a TypeScript project?

Setting up ESLint 10 flat config for TypeScript involves creating an `eslint.config.js` or `eslint.config.ts` file using flat array semantics, and enabling typescript-eslint with `projectService: true` and `tsconfigRootDir: import.meta.dirname` for type-aware linting.

How do I migrate from legacy .eslintrc to ESLint 10 flat config?

Migrating from legacy `.eslintrc.*` to ESLint 10 flat config involves translating plugins into the new `eslint.config.*` flat array shape, ensuring correct file scoping, plugin order, and running verification steps to confirm rule behavior.

How do I configure ESLint 10 to work with Prettier without conflicts?

Configuring ESLint 10 to work with Prettier without conflicts requires applying the `eslint-config-prettier` configuration last in your flat config array, which disables conflicting style rules and ensures proper coexistence between the two tools.

Can I use framework plugins like React or Next.js in ESLint 10 flat config?

Yes, you can use framework plugins like React, Vue, Next.js, Nuxt, Astro, or Storybook in ESLint 10 flat config by composing them within the flat config array while maintaining correct file scoping and plugin order for accurate linting.

Why do I need projectService true in typescript-eslint?

You need `projectService: true` in typescript-eslint to enable type-aware linting, which unlocks more accurate rules and helps avoid common monorepo path issues when configured alongside `tsconfigRootDir: import.meta.dirname` in the ESLint 10 flat config.

What is the correct file scoping for ESLint 10 flat config in a monorepo?

The correct file scoping for ESLint 10 flat config in a monorepo involves using the flat array semantics to define specific file targets for each configuration block, which, combined with `projectService: true`, prevents common monorepo path issues during type-aware linting.