eslint-config

ESLint flat config setup for monorepos requires creating an eslint.config.js file at the workspace root that re-exports from a shared config like @metasaver/core-eslint-config, mapped to your projectType (base, node, vite-web, or react-library). This centralized approach validates configurations against MetaSaver standards and enforces consistent linting rules across packages.

Flat config uses a single eslint.config.js file with direct JavaScript exports instead of JSON, enabling dynamic configuration and better monorepo support. This Skill enforces the flat config pattern with strict validation, requiring a simple re-export from shared @metasaver/core-eslint-config rather than inline rule definitions.

This Skill audits and validates existing eslint.config.js files against five required standards, including the simple re-export pattern and @metasaver/core-eslint-config dependency. If your config doesn't follow these rules, you'll need to refactor it to use the templated approach provided.

The Skill validates eslint.config.js files by checking the filename is exact, the re-export pattern is used, the shared @metasaver/core-eslint-config is imported, and npm linting scripts are defined per package or monorepo root. Validation ensures compliance with the five MetaSaver standards.

ESLint flat config requires npm scripts for linting defined at either the individual package level or monorepo root, depending on your setup. The Skill enforces this requirement as part of its validation to ensure consistent lint execution across the workspace.