Global Coding Style

Enforce universal coding standards for naming, formatting, and refactoring across codebases.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/dpietersz/pietersz.me --skill global-coding-style-dpietersz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Global Coding Style
Source: https://github.com/dpietersz/pietersz.me/tree/main/.claude/skills/global-coding-style
Command: npx skills add https://github.com/dpietersz/pietersz.me --skill global-coding-style-dpietersz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates coding conventions to improve readability, consistency, and maintainability across codebases.

Core Features & Use Cases

  • Establish naming conventions, standardized formatting, and DRY principles to reduce duplication.
  • Promote meaningful, modular functions and consistent import/asset organization across languages.
  • Use case: teams can apply these standards across repositories to unify code style and speed up onboarding.

Quick Start

Apply these standards to every new or existing code file to enforce consistent naming, formatting, and modular design.

Frequently Asked Questions about Global Coding Style

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

FAQPage Schema
How do I enforce consistent coding style across multiple programming languages?

To enforce consistent coding style across multiple languages, apply standardized naming conventions, formatting rules, and DRY principles to every new or existing code file. This unifies code style to improve readability and maintainability across repositories.

What is the best way to reduce code duplication and improve readability during refactoring?

The best way to reduce code duplication during refactoring is to apply DRY principles alongside meaningful, modular function design. Consolidating coding conventions promotes maintainable functions and standardized import organization.

Can I use universal coding standards for both new and existing codebases?

Yes, you can use universal coding standards for both new and existing codebases. Applying these standards to every file enforces consistent naming, formatting, and modular design across projects to speed up team onboarding.

Do I need specific linters or formatters configured to apply these coding conventions?

No specific linters or formatters are required. The standards operate as operational instructions within Markdown, requiring only YAML frontmatter with name and description to guide naming, formatting, and refactoring tasks.

Why does my team struggle with inconsistent naming conventions across different repositories?

Your team struggles with inconsistent naming conventions because universal coding standards are not consolidated. Establishing standardized naming, formatting, and DRY principles across repositories unifies code style and reduces onboarding friction.