Global Coding Style
Your approach to handling global coding style. Use this skill when working on files where global coding style comes into play.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install jaypaulb-canvusapi-llmdemo-global-coding-style
Repository
Skill path: .claude/skills/global-coding-style
Your approach to handling global coding style. Use this skill when working on files where global coding style comes into play.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: jaypaulb.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install Global Coding Style into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/jaypaulb/CanvusAPI-LLMDemo before adding Global Coding Style to shared team environments
- Use Global Coding Style for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: Global Coding Style description: Your approach to handling global coding style. Use this skill when working on files where global coding style comes into play. --- # 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](../../../agent-os/standards/global/coding-style.md) --- ## Referenced Files > The following files are referenced in this skill and included for context. ### ../../../agent-os/standards/global/coding-style.md ```markdown ## Coding style best practices - **Consistent Naming Conventions**: Establish and follow naming conventions for variables, functions, classes, and files across the codebase - **Automated Formatting**: Maintain consistent code style (indenting, line breaks, etc.) - **Meaningful Names**: Choose descriptive names that reveal intent; avoid abbreviations and single-letter variables except in narrow contexts. Name things by what they ARE, not what they're used for—this enables reuse - **Small, Focused Functions**: Keep functions small and focused on a single task for better readability and testability. Functions should be atoms (pure, no peer dependencies) or molecules (simple composition of 2-3 atoms). See `atomic-design.md` - **Consistent Indentation**: Use consistent indentation (spaces or tabs) and configure your editor/linter to enforce it - **Remove Dead Code**: Delete unused code, commented-out blocks, and imports rather than leaving them as clutter - **Backward compatibility only when required:** Unless specifically instructed otherwise, assume you do not need to write additional code logic to handle backward compatibility. - **DRY Principle**: Avoid duplication by extracting common logic into reusable functions or modules. However, require ≥3 real examples before abstracting—two duplications is acceptable, three warrants consideration. See `atomic-design.md` ```