Code Style & ESLint

Enforcing ESLint rules requires making lint runs mandatory and ensuring violations are never ignored. This Skill automates that enforcement by applying strict ESLint rules and TypeScript checks to maintain consistent, well-documented code.

To eliminate implicit returns and unused locals, apply TypeScript strict checks including noUnusedLocals, noImplicitReturns, and noFallthroughCases. This approach catches type errors early and removes implicit any types to improve overall codebase maintainability.

Applying naming conventions and comment guidelines across front-end and back-end projects requires enforcing standardized formatting and file-level documentation. This Skill guides components, utilities, and API routes toward strict style and documentation standards automatically.

Yes, you can use this code style enforcement for TypeScript front-end components and API routes. It applies strict TypeScript checks and ESLint rules to guide components, utilities, and API routes toward consistent style and documentation standards.

The best way to automate code quality enforcement before committing is running linting and type-checking workflows. This ensures your code adheres to strict style standards, passes mandatory lint runs, and has proper file-level documentation.

Inconsistent coding standards persist despite using a linter when violations are ignored and strict TypeScript checks are not applied. Enforcing mandatory lint runs, strict naming conventions, and mandatory file-level documentation eliminates these maintenance fragilities.