standards-enforcement

Configure ESLint, Prettier, and Husky to enforce coding standards.

90|10|Updated Nov 8, 2025
One-click install
npx skills add https://github.com/korallis/Droidz --skill standards-enforcement-korallis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standards-enforcement
Source: https://github.com/korallis/Droidz/tree/main/droidz_installer/payloads/droid_cli/default/skills/standards-enforcement
Command: npx skills add https://github.com/korallis/Droidz --skill standards-enforcement-korallis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining consistent code quality, adhering to best practices, and enforcing architectural patterns across a project, which is crucial for team collaboration and long-term maintainability.

Core Features & Use Cases

  • Automated Linting and Formatting: Integrates ESLint and Prettier to automatically check and fix code style issues.
  • Pre-commit Hooks: Implements Husky and lint-staged to ensure code quality checks are performed before commits.
  • Configuration Management: Provides sample configurations for ESLint, Prettier, and Husky.
  • Use Case: When starting a new project or onboarding a new developer, use this skill to set up the foundational code quality tools and guidelines, ensuring all code adheres to team standards from the outset.

Quick Start

Use the standards-enforcement skill to set up ESLint and Prettier for your project.

Frequently Asked Questions about standards-enforcement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up ESLint and Prettier to enforce code quality and consistency?

To enforce code quality, you configure ESLint and Prettier with sample configurations to automatically check and fix code style issues across your project. This establishes baseline formatting and linting rules for team collaboration.

What is the best way to prevent bad commits using pre-commit hooks?

Pre-commit hooks prevent bad commits by implementing Husky with lint-staged to run automated code quality checks before code is committed. This ensures only validated code adhering to team standards enters the repository.

Can I use this standards enforcement configuration for a new TypeScript project?

Yes, this configuration is applicable for starting new projects or onboarding developers to set up foundational code quality tools. It specifically supports enforcing TypeScript strict mode and defining naming conventions from the outset.

How do I configure linting rules to enforce architectural patterns and best practices?

You configure linting rules by adjusting ESLint settings to establish and enforce specific coding standards, best practices, and architectural patterns. This maintains overall code consistency and long-term project maintainability.

Does Husky with lint-staged work for running automated checks on staged files?

Yes, Husky with lint-staged works for running automated checks by ensuring code quality validation is performed specifically on staged files before commits. This targeted approach prevents formatting errors without slowing down the entire build process.