standards-enforcement

Configure ESLint, Prettier, and Husky to enforce coding standards across TypeScript projects.

3|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/Fabric-Pro/fabric-oss --skill standards-enforcement-fabric-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: standards-enforcement
Source: https://github.com/Fabric-Pro/fabric-oss/tree/main/.cursor/skills/standards-enforcement
Command: npx skills add https://github.com/Fabric-Pro/fabric-oss --skill standards-enforcement-fabric-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to maintain consistent code quality and style across a growing codebase, leading to inconsistent formatting, unchecked TypeScript errors, and style debates in code reviews. ## Core Features & Use Cases - Linter and Formatter Setup: Provides ready-to-use ESLint and Prettier configurations with recommended TypeScript rules. - Pre-Commit Automation: Configures Husky with lint-staged to run linting and formatting automatically before every commit. - Use Case: When bootstrapping a new TypeScript monorepo, use this Skill to generate the ESLint rules, Prettier settings, and pre-commit hooks so every contributor commits consistently formatted, rule-compliant code. ## Quick Start Set up ESLint, Prettier, and Husky pre-commit hooks for my TypeScript project using the standards-enforcement skill.

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 for a TypeScript project?▼

Extend eslint:recommended and plugin:@typescript-eslint/recommended in your ESLint config, then add Prettier with settings like semi, singleQuote, and tabWidth. The Skill provides ready-made JSON configurations for both tools.

How to run linting automatically before every git commit?▼

Use Husky with lint-staged to run eslint --fix and prettier --write on staged files. Configure lint-staged to target *.{js,ts,tsx} for linting and *.{json,md} for formatting.

What ESLint rules should I enforce for TypeScript strict mode?▼

Common rules include no-console as a warning, no-unused-vars as an error, and @typescript-eslint/no-explicit-any as an error. These catch unsafe patterns while keeping the build unblocked by minor issues.

Does lint-staged work with files other than JavaScript?▼

Yes, lint-staged supports glob patterns for any file type. You can run prettier --write on JSON and Markdown files while reserving ESLint for JavaScript and TypeScript sources.

When should I not enforce strict linting rules on a project?▼

Avoid strict enforcement on legacy codebases undergoing gradual migration, where thousands of existing violations would block all commits. Instead, apply rules incrementally or only to new and modified files.