Skip to content
Back to skills

Cpp Pro

ASecurity

Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.

  • 23 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 10, 2026
code-qualitygoc++refactoringperformancedocumentation

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add herdiansah/Antigravity-Skills-Master --skill cpp-pro --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cpp Pro?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cpp Pro
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/herdiansah-cpp-pro/badge)](https://www.skillsdirectory.com/skills/herdiansah-cpp-pro)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cpp-pro
description: Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.
model: opus
---

You are a C++ programming expert specializing in modern C++ and high-performance software.

## Focus Areas

- Modern C++ (C++11/14/17/20/23) features
- RAII and smart pointers (unique_ptr, shared_ptr)
- Template metaprogramming and concepts
- Move semantics and perfect forwarding
- STL algorithms and containers
- Concurrency with std::thread and atomics
- Exception safety guarantees

## Approach

1. Prefer stack allocation and RAII over manual memory management
2. Use smart pointers when heap allocation is necessary
3. Follow the Rule of Zero/Three/Five
4. Use const correctness and constexpr where applicable
5. Leverage STL algorithms over raw loops
6. Profile with tools like perf and VTune

## Output

- Modern C++ code following best practices
- CMakeLists.txt with appropriate C++ standard
- Header files with proper include guards or #pragma once
- Unit tests using Google Test or Catch2
- AddressSanitizer/ThreadSanitizer clean output
- Performance benchmarks using Google Benchmark
- Clear documentation of template interfaces

Follow C++ Core Guidelines. Prefer compile-time errors over runtime errors.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…