skills.rest
harryy2510
harryy2510COMMUNITY
Explore all skills by this author →
WebsiteGitHub

conventions

Install ESLint plugins and pre-commit hooks for JavaScript/TypeScript projects.

Updated Apr 5, 2026
Search Tags:#typescript#eslint#prettier#project-setup#coding-conventions#lint-staged#husky
One-click install
npx skills add https://github.com/harryy2510/dotclaude --skill conventions-harryy2510
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventions
Source: https://github.com/harryy2510/dotclaude/tree/main/plugins/dotclaude/skills/conventions
Command: npx skills add https://github.com/harryy2510/dotclaude --skill conventions-harryy2510

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill installs ESLint rules and pre-commit hooks to enforce coding conventions deterministically. After setup, rules cost 0 tokens — enforced by tooling, not AI.

Core Features & Use Cases

  • Install additional ESLint plugins and configure rules to standardize code quality and style.
  • Wire pre-commit hooks using Husky and lint-staged to prevent non-conforming commits.
  • Use case: apply to TypeScript/JavaScript projects to guarantee consistent linting, formatting, and commit hygiene.

Quick Start

Run the conventions skill once per project to install plugins, add rules, and wire pre-commit hooks, then commit to enforce conventions.

Frequently Asked Questions about conventions

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

FAQPage Schema
How do I enforce coding conventions across a TypeScript project using ESLint and Prettier?▼

Run the conventions skill once per project to install ESLint and Prettier plugins, update configurations, and wire Husky pre-commit hooks with lint-staged to automatically block non-conforming commits.

How do pre-commit hooks with Husky and lint-staged prevent bad commits?▼

Pre-commit hooks using Husky and lint-staged prevent bad commits by automatically running ESLint and Prettier on staged files, blocking the commit if code quality or formatting rules fail before code enters the repository.

Do I need to run project setup before applying ESLint configurations and Husky hooks?▼

Yes, running the project-setup skill is a one-time prerequisite before applying ESLint configurations and Husky pre-commit hooks to ensure deterministic installation of coding conventions across the codebase.

What is the best way to automate code formatting and linting rules in a JavaScript codebase?▼

Integrating ESLint and Prettier configurations with lint-staged and Husky pre-commit hooks guarantees deterministic code formatting and linting rules, enforcing consistent commit hygiene automatically across the codebase.

Does applying project-wide coding conventions consume AI tokens during regular development?▼

No, enforcing project-wide coding conventions costs zero tokens after setup because rules are enforced deterministically by ESLint, Prettier, and Husky tooling rather than relying on AI processing for code quality checks.

Related Skills

Explore More Software Engineering Skills→
zenbuappszenbuapps

aibdd.auto.ts.it.starter

Initialize a React integration test scaffold with Vitest, React Testing Library, and MSW.

Official
Intermediate
mia-cxmia-cx

setup-pre-commit

Automate Husky, lint-staged, and Prettier pre-commit setup in JavaScript/TypeScript repositories.

Official
Intermediate
ValyntValynt

lint-and-format

Automate ESLint, Prettier, and type-checking across a TypeScript monorepo.

Official
Advanced
walid-moswalid-mos
2

setup-pre-commit

Configure Husky pre-commit hooks with lint-staged and Prettier for JavaScript/TypeScript projects.

Community
Intermediate