C++ Pro

• Prefer value semantics by default; use std::unique_ptr for transfer of ownership.
• Use std::span, std::string_view, and references for non-owning boundaries.
• Decide early whether a subsystem uses exceptions, status objects, or std::expected style results.

Reference Guide

Bundled Scripts

• scripts/bootstrap_cpp_project.py

  • Scaffold a modern CMake baseline for library, cli, or service layouts.
  • Generates warnings policy, presets, optional sanitizers, optional clang-tidy, and starter tests.
  • Use when starting a new repository or standardizing an inconsistent baseline.

• scripts/run_cpp_quality_gates.py

  • Run configure, build, test, and optional clang-format, clang-tidy, and cppcheck steps.
  • Supports presets, explicit build dirs, optional target selection, and machine-readable reports.
  • Use before final delivery or to mirror CI locally.

• scripts/scaffold_cpp_test_template.py

  • Generate GoogleTest or Catch2 templates for unit, integration, or regression tests.
  • Use when you need consistent test structure without rewriting boilerplate each time.

• scripts/audit_cpp_project.py

  • Inspect an existing repository for CMake, tests, warnings, tooling, package-management, and CI gaps.
  • Use at the start of large refactors or when inheriting a weak or legacy C++ build.

Constraints

MUST DO

• Follow RAII and C++ Core Guidelines.
• Make ownership, lifetime, and mutability explicit in public interfaces.
• Keep CMake target-based and set the C++ standard explicitly.
• Add or update tests for all behavior changes.
• Use strict warnings and run relevant sanitizers or static analysis when available.
• Explain tradeoffs around exceptions, status returns, template constraints, and ABI stability.

MUST NOT DO

• Use raw owning new/delete in normal application code.
• Hide ownership transfer or thread-safety assumptions.
• Mix incompatible error-handling models inside the same subsystem without a strong boundary reason.
• Put using namespace std in headers.
• Ship performance claims without profiling, benchmarking, or at least a concrete measurement plan.
• Rewrite large legacy areas all at once when an incremental migration path exists.

Output Template

For non-trivial C++ tasks, provide:

1. Toolchain and architecture summary.
2. Interface and ownership decisions.
3. Implementation notes and notable C++20/23 features used.
4. Build, test, and tooling changes.
5. Risk notes, migration impact, and performance considerations.

Primary References

• cppreference
• CMake Documentation
• C++ Core Guidelines
• GoogleTest Documentation
• Catch2 Documentation
• clang-tidy Documentation
• AddressSanitizer Documentation