Enforces LPC coding conventions for oxidus-mudlib repository modules.
npx skills add https://github.com/gesslar/oxidus-mudlib --skill lpc-coding-style
Please help me install this Agent Skill. Skill: lpc-coding-style Source: https://github.com/gesslar/oxidus-mudlib/tree/main/.claude/skills/lpc-coding-style Command: npx skills add https://github.com/gesslar/oxidus-mudlib --skill lpc-coding-style
LPC coding style and formatting conventions ensure that all LPC work in the oxidus-mudlib project adheres to a single, readable standard, reducing onboarding time and merge conflicts.
Consult this guide before writing or modifying any LPC code to ensure consistent project-wide style.
High-intent search queries and answers about installing and using this skill.
Standard LPC coding conventions require 2-space indentation, specific bracing styles, camelCase naming, and LPCDoc-compliant comments for public APIs to ensure consistent readability across modules.
Format visibility modifiers explicitly on globals and functions, and prefix private file-global variables with a double underscore (__), keeping modules private by default to enforce strict encapsulation.
Apply these coding style rules when creating new LPC objects, updating existing modules, or refactoring code to align with project-wide conventions and reduce merge conflicts.
LPC files must use 2-space indentation, eliminate all trailing whitespace, and include exactly one single trailing newline at the end of the file to maintain clean formatting.
Consistent naming conventions and access modifiers in LPC reduce onboarding time and merge conflicts by enforcing a single readable standard across the entire repository codebase.
gesslarImplement Oxidus combat mechanics for NPCs and players in LPC.
fossuavCheck modified C++ and header files for style violations using astyle and git diff.
gesslarGenerate LPCDoc comment blocks for LPC functions, classes, and modules.
FilenCloudDiensteAnalyze project configuration and source code to enforce style conventions.
