cc-c-project-standard
Use when Pure C module interfaces, ownership contracts, error-code cleanup paths, build conventions or C engineering validation need design or review.
SKILL.mdskills/cc-c-project-standard/SKILL.md
GitHubC project engineering
Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language.
Read the existing C standard, compiler flags, build system and exported ABI. Preserve symbol visibility, calling conventions and error codes.
Apply the workflow
- Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now.
- Apply the specialist checks, establishing the input evidence before selecting the smallest change.
- Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result.
- Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only.
Task boundary
C++ resource abstractions and exceptions are not a replacement for a pure C contract; cross-language memory incidents have a dedicated specialty.
Engineering practices
Read the local engineering decisions for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.