C Patterns

This skill focuses on safe C: explicit ownership, explicit errors, predictable control flow, and contracts that survive refactors.

If you’re writing tests, use c-testing.

When to activate

• Writing/refactoring C modules and APIs
• Reviewing for memory safety and integer safety
• Designing error-handling conventions and cleanup paths
• Hardening code for sanitizer/static analysis adoption
• Porting C code across GCC/Clang/MSVC/MinGW

Core rules (high signal)