- Home
- Skills
- Ehtbanton
- Claudeskillsrepo
- Eslint Config Generator
eslint-config-generator_skill
- TypeScript
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill ehtbanton/claudeskillsrepo --skill eslint-config-generator- SKILL.md1.9 KB
Overview
This skill generates production-ready ESLint configuration files (.eslintrc.js, .eslintrc.json, or eslint.config.js) for JavaScript and TypeScript projects. It produces framework-aware configs (React, Node, Next.js, etc.) and supports both legacy and modern flat ESLint formats for v8/v9+. The output is ready to paste or save and includes plugins, parsers, extends, and sensible rule sets.
How this skill works
On invocation it inspects the requested project type and target format (legacy .eslintrc or modern flat eslint.config.js) and emits a complete config with parserOptions, plugins, recommended extends, and tuned rules. It can include TypeScript parser/plugin setup, React and hooks rules, Node/Next specifics, and common stylistic or error-prevention rules. The generator defaults to ESLint 8/9 compatibility and flags recommended rule severities.
When to use it
- Starting a new JavaScript or TypeScript project and you need a ready ESLint config
- Migrating from legacy .eslintrc to ESLint flat config (eslint.config.js)
- Adding framework-specific linting: React, Next.js, Node, or Vue
- Enforcing TypeScript rules with @typescript-eslint parser and plugin
- Creating CI lint jobs that require consistent, production-ready rules
Best practices
- Choose eslint.config.js (flat) for ESLint v9 and modern toolchains; use .eslintrc.js for legacy support
- Include project tsconfig.json in parserOptions.project when linting types with TypeScript
- Start with recommended extends and then enable stricter rules progressively
- Keep stylistic rules minimal in base config and enforce team style with a separate shareable config if needed
- Run ESLint in CI and enable autofix for safe, mechanical fixes before committing
Example use cases
- Generate eslint.config.js for a React + TypeScript app with react/recommended, react-hooks, and @typescript-eslint rules
- Create a .eslintrc.js for a Node service using CommonJS, targeting Node 18 and enabling no-console only for production builds
- Produce a flat config that scopes TypeScript rules to **/*.ts,**/*.tsx files and uses the TypeScript parser
- Provide a minimal JSON config for a small JavaScript library that only needs eslint:recommended and basic stylistic rules
FAQ
Use eslint.config.js (flat) for ESLint v9 and modern projects; use .eslintrc.js when you need compatibility with older tooling or ESLint v8.
Does the generator include TypeScript type-aware rules?
Yes — it can add @typescript-eslint with parserOptions.project pointing at ./tsconfig.json so type-aware rules work when desired.