What problem does it solve? Enforcing consistent code conventions across a codebase or monorepo is difficult to do manually, and large-scale refactors often lack a deterministic way to measure compliance. This Skill guides the configuration of oxlint and eslint rules so conventions are enforced automatically by the linter. ## Core Features & Use Cases - Oxlint-first linting: Uses oxlint, a Rust-based drop-in replacement for eslint, as the default linter. - Rule configuration guidance: Covers max-lines-per-function, max-params, max-lines, max-depth, and restricted globals such as navigator, window, and document. - Boundary enforcement: Uses @boundaries/eslint-plugin to control which files can import internal or external dependencies and to make nested files private to siblings or parent files. - Use Case: When refactoring a monorepo, enable a rule across the entire codebase, run the linter to count violations, automate the fixes, and repeat until the codebase is compliant. ## Quick Start Configure oxlint rules to restrict direct usage of window and document globals in my TypeScript project.