Use modern C++ deliberately
Apply RAII, value semantics, smart pointers, templates, concepts, ranges, exceptions, and move behavior according to project standards.
Codex Skills for C++ give Codex a careful workflow for navigating large codebases, managing ownership and lifetime, using modern language features, handling concurrency, building with CMake, testing behavior, and diagnosing performance. Download the skills for C++ work where undefined behavior and platform details matter.
task: complete c++ development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffStrong c++ development work depends on context, explicit decisions, and checks that match the real environment.
These skills give Codex a specialist workflow for c++ development while preserving local conventions, important constraints, and human review.
Apply RAII, value semantics, smart pointers, templates, concepts, ranges, exceptions, and move behavior according to project standards.
Make resource, pointer, view, iterator, callback, and thread lifetime explicit across interfaces.
Handle synchronization, atomics, cancellation, memory ordering, files, networking, libraries, and platform APIs.
Run builds, tests, warnings, static analysis, sanitizers, fuzzing, benchmarks, and profiling where supported.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Read language standard, compilers, platforms, CMake targets, flags, dependencies, generated code, and tests.
Follow ownership, aliases, errors, thread access, binary boundaries, and caller expectations.
Prefer clear RAII designs, preserve compatibility, isolate platform code, and avoid speculative rewrites.
Build relevant configurations, test, enable warnings and sanitizers, analyze, fuzz, or profile according to risk.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Develop engines, runtimes, services, drivers, storage, networking, and native tools.
Design APIs, ownership contracts, ABI boundaries, compatibility, packaging, examples, and tests.
Build performance-sensitive engine, rendering, simulation, tooling, and gameplay systems.
Work with constrained resources, hardware interfaces, cross-compilation, and deterministic behavior.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable c++ development work with a visible process.
Build and maintain native applications, libraries, systems, and tools.
Work on performance-sensitive code with explicit memory and platform behavior.
Control resources, concurrency, binary interfaces, and operational constraints.
Introduce safer patterns incrementally while preserving compatibility.
The skills assist C++ engineering, but safety-critical code, low-level concurrency, ABI changes, embedded targets, and security-sensitive components require expert review.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with the included c++ development guidance, checks, and supporting files.
Use project scope for local rules and versions, or personal scope for a reusable workflow.
Document the tools, audience, standards, source material, constraints, and approval rules for this c++ development work.
Provide the intended outcome, important edge cases, required checks, and expected handoff.
Practical answers about capabilities, limits, setup, and review.
The workflow follows the standard, compilers, and compatibility targets defined by the project.
Yes. They can inspect and edit targets, properties, dependencies, presets, tests, installation, and packaging.
They can trace ownership and use compiler diagnostics, sanitizers, static analysis, tests, and debugging tools.
Yes. They can design and debug generic code while considering diagnostics, compilation cost, and API clarity.
They profile before changing algorithms, data layout, allocations, vectorization, or concurrency.
Clear context. Purposeful work. Relevant checks. A result others can understand.