Enforce ik_ prefix and module abbreviations for ikigai C codebase symbols.
npx skills add https://github.com/mgreenly/ikigai --skill naming-mgreenly
Please help me install this Agent Skill. Skill: naming Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/naming Command: npx skills add https://github.com/mgreenly/ikigai --skill naming-mgreenly
Inconsistent naming across modules leads to confusion and maintenance burden. The Naming Conventions skill consolidates rules and enforces a uniform symbol prefix and abbreviation usage across the ikigai C codebase.
Follow the documented naming conventions when creating new symbols and modules to ensure consistency and readability.
High-intent search queries and answers about installing and using this skill.
A prefix policy like ik_ combined with module-based abbreviations such as cfg, msg, and ctx enforces consistent C naming conventions. This approach ensures readability and reduces maintenance burden across the entire codebase.
Common module abbreviations for C codebase symbols include cfg, msg, ctx, conn, req, resp, buf, len, str, ptr, tmp, err, res, ws, sess, and corr. These abbreviations ensure consistent symbol prefixes across module subdirectories.
To organize modules when applying naming conventions in C, require one subdirectory per module and enforce consistent symbol prefixes across all files within it. This structure aligns new modules automatically and reduces onboarding effort.
Inconsistent symbol naming causes maintenance problems in C projects because varying prefixes and abbreviations across modules lead to confusion. Consolidating rules into a uniform prefix policy ensures readability and reduces review time.
Yes, you can use standard abbreviations like cfg, conn, req, and resp for new modules in an ikigai C codebase. Establishing a single prefix policy and using these abbreviations automatically aligns new symbols with existing conventions.
Fr-e-dAnalyze project directory structures to generate architectural summaries.
benediktmsCheck code against project linter conventions for naming, formatting, and structure.
neilpetersonScan Azure Bicep templates for security misconfigurations and compliance violations.
causify-aiFormat Python code with black and autopep8 for PEP8 compliance.
