C++ Coding Standards
Modern C++ (17/20/23) for Muse, from the C++ Core Guidelines: RAII, const-correctness, smart pointers, concepts, and error handling, with rule numbers and DO/DON'T pairs.
- What
- Modern C++ (17/20/23) for Muse, from the C++ Core Guidelines: RAII, const-correctness, smart pointers, concepts, and error handling, with rule numbers and DO/DON'T pairs.
- Cost
- Free
- Needs
- Use "C++ Coding Standards" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: C++ coding standards derived from the C++ Core Guidelines (isocpp.github.io) that make Muse write modern, safe, idiomatic C++17/20/23. Organized by guideline area with rule numbers you can cite: philosophy and interfaces (express intent, statically type-safe, no resource leaks, immutability by default), functions (single logical operation, constexpr and noexcept where fitting, return values over output parameters, F.16 parameter passing), classes (Rule of Zero or Rule of Five, explicit single-argument constructors, virtual destructors), resource management (RAII everywhere, raw pointer means non-owning, unique_ptr over shared_ptr, make_shared, never naked new/delete), expressions (always initialize, {} syntax, const by default, nullptr not NULL, no C-style casts), error handling (throw by value, catch by reference, custom exception types, destructors never fail), const-correctness (Con.1 to Con.5), concurrency (scoped_lock, never call unknown code under a lock, no volatile for synchronization), templates with C++20 concepts, standard library preferences (vector by default, string_view to observe, '\n' not endl), enumerations (enum class, no ALL_CAPS), source file and naming conventions (include guards, no using namespace in headers, underscore_style), and performance (don't optimize without measurements). Every section ships DO/DON'T pairs plus a quick-reference completion checklist. Use when writing, reviewing, or refactoring C++ code, making architectural decisions, or enforcing consistent style across a codebase. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the full Core Guidelines are vast, this is the working subset; embedded and bare-metal contexts may need selective adaptation; the skill guides, the compiler and your reviewers still decide. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "C++ Coding Standards" with your Muse. Prerequisites: none to install. Pure guidance; a C++17 or newer codebase helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/cpp-coding-standards/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review (or write) this C++ code against the Core Guidelines: [paste code or describe the task]." 3. Ask it to cite rule numbers (R.11, ES.20, Con.1) for every finding, with DO/DON'T pairs. Tip: paste a legacy file and ask what to modernize first for the biggest safety win. Safety: a skill is plain-text instructions; it runs nothing by itself. The compiler is the final judge; review before merging.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.