6 skills found
Deep linter reference for authoring or debugging a vigiles enforce() rule — plugin tables, AST selectors, type-aware rules, auto-fix, and edge cases for ESLint, Ruff, Pylint, RuboCop, Stylelint, and Clippy. Use when you need the exact rule name or config for a specific linter, not for running a linter. (JVM/Go linters — detekt, ktlint, Checkstyle, golangci-lint — and Cedar have no deep-dive file yet; their reference lives in docs/linter-support.md.)
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
Coding style standards enforced by Prettier and ESLint. Use this skill when writing JavaScript, HTML, CSS, or JSON to ensure consistent formatting, naming conventions, and code quality. Apply when creating new files, refactoring code, or ensuring adherence to automated formatting rules.
Enforce semantic CSS variable theming in Tailwind projects. Prevents raw colors (hex, rgb) and non-theme Tailwind classes. Use when project has semantic tokens, CSS vars, or custom ESLint theming rules.
Run ESLint and Prettier validation to check code style, formatting, and best practices. Returns structured output with error/warning counts, rule violations, and affected files. Used for code quality gates and pre-commit validation.
Configure and enforce code quality with AI-assisted linting. Activate when users mention"configure linting", "eslint setup", "code quality rules", "linting configuration",or "code standards". Handles linting tool configuration.
