What problem does it solve? Setting up ESLint for a Next.js/React/TypeScript codebase often produces hundreds of errors from overly strict rules, blocking CI and forcing teams to choose between disabling linting entirely or drowning in false positives. ## Core Features & Use Cases - Ready-to-use flat config template: A complete eslint.config.js combining typescript-eslint, react, react-hooks, jsx-a11y, import, and @next/next plugins with sensible defaults. - Rule severity tuning guidance: Explains which rules to downgrade to warn (e.g., no-explicit-any) and which to disable (e.g., react-hooks/set-state-in-effect) with documented rationale. - Common pitfall fixes: Covers flat-config glob issues like using **/*.cjs instead of *.cjs to match files in subdirectories. - Use Case: You inherit a large Next.js monorepo where pnpm lint fails with 500 errors. Apply this config template to get CI passing immediately while tracking real issues as warnings. ## Quick Start Ask the AI to set up an optimized ESLint flat config for my Next.js TypeScript project that passes CI without disabling important rules.
