coding-guidance-cpplisted

# C++ Coding Guidance This skill adds portable C++ implementation, refactoring, and review guidance. ## Adjacent Skills This skill provides portable C++ engineering principles. Compose with: - **Workflow:** **thinking** (ambiguous decision framing), **recursive-thinking** (stress-testing), **security** (threat modeling) - **Domain overlays:** **backend-guidance** (server-side code), **backend-systems-guidance** (stronger backend architecture, reliability, and trust-boundary work), **ui-guidance** (graphical UI/web frontend), **project-core-dev** (repo-specific completion discovery and reporting when needed) - **Qt specialization:** **coding-guidance-qt** when Qt object lifetime, eventing, widgets, models, thread affinity, or generated build steps dominate ## When Not to Lean on This Skill - non-C++ work - legacy or bare-metal environments where modern C++ guidance must be adapted selectively - pure architecture or process work with no C++ design or code judgment needed - repo-specific style packs or platform policies that should be enforced by local `clang-tidy`, compiler, or overlay rules rather than a portable principle skill ## Boundary Contract Keep this skill focused on portable C++ engineering judgment. - Put repo-specific exception policy, warning policy, formatter choices, and include-order rules in repo config or repo docs - Put style-pack rules from ecosystems such as Google, LLVM, Abseil, or platform/vendor bundles in repo config