standards-enforcement
Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.
When & Why to Use This Skill
This Claude skill automates the establishment and enforcement of coding standards, architectural patterns, and best practices across your codebase. By leveraging industry-standard tools like ESLint, Prettier, and Husky, it ensures consistent code quality, minimizes technical debt, and streamlines the code review process through automated linting, formatting, and pre-commit hooks.
Use Cases
- Project Initialization: Setting up a comprehensive linting and formatting foundation using ESLint and Prettier for new or existing repositories.
- Workflow Automation: Implementing Husky and lint-staged to enforce quality checks automatically during the git commit process, preventing substandard code from entering the version control.
- Team Standardization: Defining and enforcing unified naming conventions, directory structures, and architectural rules to maintain consistency across large engineering teams.
- Type Safety Enhancement: Configuring and enforcing TypeScript strict mode and custom rules to improve runtime reliability and developer productivity.
- Architectural Governance: Conducting automated architecture reviews to ensure code follows established design patterns and import organization rules.
| name | standards-enforcement |
|---|---|
| description | Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards. |
Standards Enforcement - Maintaining Code Quality
When to use this skill
- Setting up ESLint, Prettier, and code formatters
- Configuring linting rules and code standards
- Creating team code style guides
- Implementing pre-commit hooks with Husky
- Establishing naming conventions
- Enforcing TypeScript strict mode
- Maintaining code consistency across team
- Conducting code review for standards compliance
- Defining architectural patterns and rules
- Setting up import ordering and organization
- Enforcing test coverage requirements
- Creating and maintaining coding guidelines
When to use this skill
- Setting up project guidelines, code reviews, enforcing best practices, maintaining consistency.
- When working on related tasks or features
- During development that requires this expertise
Use when: Setting up project guidelines, code reviews, enforcing best practices, maintaining consistency.
Tools
ESLint
{
"extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended"],
"rules": {
"no-console": "warn",
"no-unused-vars": "error",
"@typescript-eslint/no-explicit-any": "error"
}
}
Prettier
{
"semi": true,
"singleQuote": true,
"tabWidth": 2,
"trailingComma": "es5"
}
Husky + lint-staged
{
"lint-staged": {
"*.{js,ts,tsx}": ["eslint --fix", "prettier --write"],
"*.{json,md}": ["prettier --write"]
}
}