01
- Rescue
- A linter that will not load, a pre-commit hook that blocks every developer, or a CI check firing thousands of warnings. We get it passing before we decide what to keep.
02
- Flat config migration
- Converting eslintrc to the new eslint.config.js format, validating plugin compatibility, and running a diff of what the new config would flag before anyone merges it.
03
- Ruleset tuning
- Pruning inherited presets, enabling rules that actually catch bugs in your stack, and turning off the ones that produce only noise for your codebase.
04
- Performance
- Caching, scoped project references, parallel linting and eslint-plugin-perf-standard, with the before and after wall-clock measured on your real repo.
05
- Custom rules
- Writing project-specific rules for patterns code review keeps flagging, so the linter enforces them automatically instead.
06
- Managed Tech
- A regular review of the ruleset as the project and the ecosystem change, with minor version upgrades handled quietly in the background.