# Olore Eslint 10.5.0

> Local ESLint documentation reference (10.5.0). ESLint documentation. Use for JavaScript/TypeScript linting, rules, flat config, plugins, custom rules, and code quality enforcement.

- Skill: `olorehq/olore-eslint-10-5-0` (Agent Skill, multi-file: 358 files)
- Install (CLI): `npx get-skill add olorehq/olore-eslint-10-5-0`
- Raw SKILL.md: https://api.skillmd.com/api/skills/olorehq/olore-eslint-10-5-0/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: olorehq (https://skillmd.com/u/olorehq)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/olorehq/olore-eslint-10-5-0

---


# ESLint Documentation

ESLint is a static analysis tool for JavaScript and TypeScript. Use this skill when working with ESLint configuration, built-in rules, custom rules, plugins, the CLI, or the Node.js API.

## Quick Reference

| Task | Entry Point |
|------|-------------|
| Getting started | `contents/use/getting-started.md` |
| Flat config (eslint.config.js) | `contents/use/configure/configuration-files.md` |
| Migrate eslintrc to flat config | `contents/use/configure/migration-guide.md` |
| Migrate to v10 | `contents/use/migrate-to-10.0.0.md` |
| Rule reference | `contents/rules/{rule-name}.md` |
| CLI reference | `contents/use/command-line-interface.md` |
| Custom rules | `contents/extend/custom-rules.md` |
| Plugins | `contents/extend/plugins.md` |
| Node.js API | `contents/integrate/nodejs-api.md` |
| Troubleshooting | `contents/use/troubleshooting/index.md` |

## When to use

Use this skill when the user asks about:
- Configuring ESLint (flat config, plugins, rules, parsers, ignores)
- Specific built-in lint rules and their options
- Writing custom lint rules or plugins
- CLI usage and options
- Integrating ESLint via the Node.js API
- Migrating to ESLint v10 or from eslintrc to flat config
- TypeScript or non-JS language linting setup
- Suppressing, disabling, or tuning lint warnings

## How to find information

1. **First**, read `TOC.md` for complete file listing organized by directory
2. Identify relevant section based on user's question
3. Read specific files for details

**TOC.md contains all files organized by directory - always check it first.**

