C++ Core Guidelines

Overview

Use this skill to apply modern C++ guidance derived from the ISO C++ Core Guidelines. Prefer safer, clearer, statically checkable C++ without sacrificing zero-overhead design.

Workflow

1. Identify the task shape: new design, implementation, refactor, modernization, review, or bug fix.
2. Read references/core-guidelines-condensed.md when the task touches C++ behavior, APIs, ownership, templates, concurrency, performance, or code review.
3. Apply the guidelines pragmatically:
   • Prefer explicit interfaces, strong types, invariants, RAII, standard-library facilities, and compile-time checking.
   • Preserve project conventions when they conflict only cosmetically.
   • Treat raw ownership, unchecked bounds, data races, invalid lifetimes, implicit global state, naked allocation, C casts, and macro-based code as high-priority risks.
4. When reviewing, lead with concrete bugs and maintenance risks, not style preferences. Reference the relevant Core Guidelines family, such as R for resources, F for functions, or CP for concurrency.
5. When changing code, keep edits scoped, add regression tests for behavior changes, and prefer mechanical/tool-enforceable improvements.

Resource