naming

Enforce ik_MODULE_THING symbol prefixes and module-per-directory structure in the ikigai C codebase.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/multicam/ikigai-rev --skill naming-multicam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/naming
Command: npx skills add https://github.com/multicam/ikigai-rev --skill naming-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Naming conventions for the ikigai C codebase, providing a consistent approach to symbol prefixes, module organization, and abbreviations to improve readability and maintainability.

Core Features & Use Cases

  • Standardized symbol naming: ik_MODULE_THING prefixes for functions, types, and globals.
  • Module isolation: one subdirectory per module to ensure cohesive symbol namespaces.
  • Approved abbreviations: enforce common short forms (cfg, msg, ctx, conn, req, resp, buf, len, str, ptr, tmp, err, res, ws, sess, corr).
  • Use case: when adding a new module, apply the naming rule to all new symbols to maintain consistency.

Quick Start

Update a module's first public symbol to use the ik_<module>_<thing> pattern.

Frequently Asked Questions about naming

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

FAQPage Schema
How do I enforce consistent naming conventions in a C codebase?

To enforce consistent C naming, apply the ik_MODULE_THING prefix pattern to all functions, types, and globals. Require a module-per-directory structure and use approved abbreviations like cfg, ctx, and req to improve readability and maintainability.

What are the approved abbreviations for C module symbols?

Approved C module symbol abbreviations include cfg, msg, ctx, conn, req, resp, buf, len, str, ptr, tmp, err, res, ws, sess, and corr. Enforcing these common short forms maintains consistency across the codebase.

How do I structure C modules to ensure cohesive symbol namespaces?

Structure C modules for cohesive namespaces by enforcing a module-per-directory structure. Isolate each module in its own subdirectory and apply the ik_MODULE_THING prefix to all public symbols to maintain reliable code organization.

How do I add a new module to the ikigai C codebase?

To add a new module to the ikigai C codebase, create a dedicated subdirectory for module isolation. Apply the ik_MODULE_THING naming pattern to all new symbols and use frontmatter-driven definitions for name and description to enable discovery.

Does the C naming convention require frontmatter for module discovery?

Yes, the C naming convention requires frontmatter-driven definitions of name and description for each module. This frontmatter enables automated checks and module discovery across the ikigai codebase while maintaining standardized naming.

Why use standardized symbol prefixes for C codebase modules?

Use standardized symbol prefixes like ik_MODULE_THING for C codebase modules to improve readability and maintainability. Consistent prefixes prevent symbol collisions and provide a clear, reliable approach to module organization.