eslint-config

Configure ESLint flat config with TypeScript parser and custom rules.

4|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/mcclowes/lea --skill eslint-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eslint-config
Source: https://github.com/mcclowes/lea/tree/main/.claude/skills/eslint-config
Command: npx skills add https://github.com/mcclowes/lea --skill eslint-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

ESLint configuration best practices for Lea projects, including flat config, TypeScript integration, and custom rules.

Core Features & Use Cases

  • Flat config: Modern ESLint setup with flat config style
  • TypeScript integration: TS parser options and recommended rules
  • File-specific rules: Scoped overrides for tests and scripts

Quick Start

Set up eslint.config.js as shown and run lint tasks.

Frequently Asked Questions about eslint-config

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

FAQPage Schema
How do I configure ESLint for a TypeScript project using flat config?

Flat config is ESLint's modern configuration format. Set up an eslint.config.js file with TypeScript parser options and recommended rules for your project, replacing legacy .eslintrc formats with a flatter, more maintainable structure.

Can I apply different ESLint rules to specific files like tests and scripts?

Yes, flat config supports file-specific rule overrides. You can scope rules to test directories, script folders, or other file patterns within a single configuration, applying stricter or relaxed rules where appropriate.

What's the best way to integrate TypeScript with ESLint in a flat config setup?

Integrate TypeScript by configuring the ESLint TypeScript parser, enabling language service features, and applying TypeScript-specific recommended rules in your flat config. Project references can be used to optimize type checking across your codebase.

Do I need to migrate from a legacy ESLint configuration to flat config?

Migration to flat config is recommended for modern projects. Flat config offers cleaner syntax, better scoping, and improved maintainability. The migration process involves converting your existing .eslintrc or config files to eslint.config.js format.

How do I enforce custom naming conventions and linting policies across my codebase?

Use flat config to define naming-convention rules and custom lint policies that apply project-wide or to specific scopes. Run lint tasks to enforce these policies consistently during initial setup and ongoing development.

What are the limitations of flat config for managing multiple TypeScript projects?

Flat config handles project references effectively, but complex monorepo setups may require careful scoping. Be aware that overrides must be explicit per file pattern, and large rulesets can impact linting performance.