coding-standard-c
C Coding Standards
When reviewing or generating C code, follow these rules:
File Naming
- Source files: snake_case with
.cextension (e.g.,user_service.c,data_parser.c) - Header files: snake_case with
.hextension (e.g.,user_service.h,data_parser.h) - Keep names short but descriptive (max ~20 characters)
Header Guards
- Format: UPPER_SNAKE_CASE with
_Hsuffix - Include path in guard: (e.g.,
PROJECT_MODULE_FILE_H)
#ifndef USER_SERVICE_H
#define USER_SERVICE_H
// content
#endif /* USER_SERVICE_H */
More from jdubray/puffin
coding-standard-cpp
Enforce C++ coding standards including camelCase or snake_case variables, PascalCase classes, and consistent file naming.
26coding-standard-java
Enforce Java coding standards including camelCase variables, PascalCase classes, and PascalCase filenames matching class names.
23coding-standard-python
Enforce Python PEP 8 coding standards including snake_case variables, PascalCase classes, and snake_case filenames.
20coding-standard-javascript
Enforce JavaScript/ES6+ and TypeScript coding standards including camelCase variables, PascalCase classes, and kebab-case filenames.
18modularity-patterns
Recommends modularity, composition, and decoupling patterns for design challenges. Use when designing plugin architectures, reducing coupling, improving testability, or separating cross-cutting concerns.
17rlm
Run a Recursive Language Model-style loop for long-context tasks. Uses a persistent local Python REPL and an rlm-subcall subagent as the sub-LLM (llm_query).
1