global-coding-style
Coding style standards enforced by Prettier and ESLint. Use this skill when writing JavaScript, HTML, CSS, or JSON to ensure consistent formatting, naming conventions, and code quality. Apply when creating new files, refactoring code, or ensuring adherence to automated formatting rules.
When & Why to Use This Skill
This Claude skill automates the enforcement of global coding standards using Prettier and ESLint. It ensures consistent formatting, naming conventions, and high code quality across JavaScript, HTML, CSS, and JSON files, helping developers maintain a clean, professional, and maintainable codebase through automated rule adherence.
Use Cases
- Standardizing Codebases: Automatically applying Prettier and ESLint rules to JavaScript, HTML, and CSS files to ensure a uniform look and feel across the entire project.
- Refactoring for Readability: Improving code quality by renaming variables to be more descriptive and breaking down large, complex functions into smaller, focused tasks.
- Pre-commit Optimization: Cleaning up code by removing unused imports, dead code, and commented-out blocks to ensure the repository remains lean and passes lint-staged hooks.
- Enforcing Best Practices: Applying the DRY (Don't Repeat Yourself) principle to eliminate code duplication and ensure adherence to modern software engineering standards.
| name | Global Coding Style |
|---|
When to use this skill
- When writing JavaScript in any .js file to follow consistent naming and formatting
- When ensuring Prettier formatting is applied correctly to .html, .css, .js, .json, and .md files
- When choosing meaningful, descriptive variable and function names
- When keeping functions small and focused on a single task
- When removing dead code, unused imports, or commented-out blocks
- When applying DRY principle to avoid code duplication
- When writing code that will pass lint-staged pre-commit hooks
Global Coding Style
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global coding style.
Instructions
For details, refer to the information provided in this file: global coding style