cpp-dev-guidelines

Provides design, formatting, CI/CD and testing standards for C++17/20 projects.

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/NmBoyd/claude_setup --skill cpp-dev-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cpp-dev-guidelines
Source: https://github.com/NmBoyd/claude_setup/tree/main/.claude/skills/cpp-dev-guidelines
Command: npx skills add https://github.com/NmBoyd/claude_setup --skill cpp-dev-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

C++ projects often drift away from consistent modern practices; this Skill provides structured guidelines to standardize design, formatting, testing, and build configurations across teams.

Core Features & Use Cases

  • Enforces RAII, smart pointers, and safe resource management patterns.
  • Provides project-structure recommendations (include/src, CMake, CI tooling) and common idioms (RAII, PIMPL, CRTP, etc.) for maintainability.
  • Serves as a reference during onboarding, code reviews, and architecture decisions for C++17/20 projects.

Quick Start

Audit an existing module and implement at least two recommended patterns.

Frequently Asked Questions about cpp-dev-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for standardizing modern C++ project structure?

C++17/20 maintainable architecture requires standardizing include/src directory layouts, configuring CMake build systems, and integrating CI tooling. This Skill codifies these guidelines to standardize formatting, testing, and build configurations across teams.

How do I enforce RAII and smart pointers for safe resource management in C++?

Enforce RAII and smart pointers in C++ by applying codified development practices that standardize safe resource management patterns. This Skill provides structured guidelines to help teams consistently implement RAII, PIMPL, and CRTP for robust code.

Does this C++ development guidelines Skill apply to legacy codebases or only new projects?

These C++ development guidelines apply to both new and existing C++17/20 projects. You can audit an existing module and implement at least two recommended patterns, or use the guidelines as a reference during onboarding and code reviews.

What's the best way to standardize code review processes for C++17/20 projects?

The best way to standardize C++17/20 code reviews is to codify project structure, common idioms, and testing standards into a reusable reference. This Skill serves as a standardized review checklist to ensure consistent architecture and safe resource management across teams.

When should I not use automated static analysis for C++ code quality?

Static analysis should be paused when refactoring complex C++ template hierarchies or legacy macro logic that generates false positives, as automated tools may misinterpret unsafe resource management patterns. Rely on manual code reviews against established guidelines before re-enabling strict CI tooling checks.