# Global Coding Style > Write clean, maintainable code with consistent naming conventions, meaningful identifiers, small focused functions, proper formatting, and adherence to DRY principles. Use this skill when writing code in any programming language (TypeScript, JavaScript, Python, Ruby, Go, etc.); when naming variables, functions, classes, and files; when formatting code with consistent indentation and line breaks; when refactoring code to follow DRY principles and avoid duplication; when writing small, focused functions with single responsibilities; when removing dead code, commented-out blocks, and unused imports; when choosing between backward compatibility and clean implementations; when structuring code for readability and testability; when applying automated formatting with Prettier, ESLint, Black, RuboCop, or similar tools; or when establishing and maintaining coding standards across the project. Use when this capability is needed. - Skill: `tomevault-io/global-coding-style` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/global-coding-style` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/global-coding-style/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/global-coding-style --- # 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. ## When to use this skill - When establishing naming conventions for variables, functions, classes, and files - When writing small, focused functions with single responsibilities - When applying automated formatting and consistent indentation - When choosing meaningful names that reveal intent - When removing dead code and unused imports - When refactoring to follow DRY principles and avoid duplication - When deciding on backward compatibility vs. clean implementations - When structuring code for readability and testability - When working with TypeScript, JavaScript, Python, Ruby, or any programming language ## Instructions For details, refer to the information provided in this file: [global coding style](../../../agent-os/standards/global/coding-style.md) --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/shynlee04) — claim your Tome and manage your conversions.