cc-cpp-project-standard
/cc-cpp-project-standard
Use when C++ module/header boundaries, resource lifetime, exception safety, ABI, build-standard conventions or project-wide C++ checks need design or review.
- Author
- bovinphang ↗
- Repository
- backend-craft ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 10
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when C++ module/header boundaries, resource lifetime, exception safety, ABI, build-standard conventions or project-wide C++ checks need design or review.
Original author description
Use when C++ module/header boundaries, resource lifetime, exception safety, ABI, build-standard conventions or project-wide C++ checks need design or review.
How it works
- Apply the workflow
- Task boundary
- Engineering practices
SKILL.md preview
--- name: cc-cpp-project-standard description: "Use when C++ module/header boundaries, resource lifetime, exception safety, ABI, build-standard conventions or project-wide C++ checks need design or review." --- # C++ project engineering Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language. Read the actual C++ standard, standard library, compiler matrix, build presets and exported ABI before choosing features. ## Apply the workflow 1. Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now. 2. Apply the [specialist checks](references/practice.md), establishing the input evidence before selecting the smallest change. 3. Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result. 4. Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only. ## Task boundary Do not upgrade the C++ standard or replace the build system without a task need; pure C interfaces retain their own contract. ## Engineering practices Read the [local engineering decisions](references/engineering-practices.md) for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.
Files in this package (10)
- SKILL.md 1 KB
- examples/engineering/README.md 1 KB
- examples/engineering/boundary.cpp 1 KB
- examples/engineering/boundary.hpp 1 KB
- examples/engineering/boundary_test.cpp 2 KB
- references/engineering-practices.md 5 KB
- references/practice.md 2 KB
- references/common/engineering-practices.md 12 KB
- references/common/engineering-practices.rules.json 2 KB
- references/common/engineering-practices.sources.json 16 KB
Versions
The database has no other skills named cc-cpp-project-standard.
Database snapshot: 13.11.2026 · package version 95b51aa9d08f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90cc-java-project-standard
Use when Java package/module structure, build-tool conventions, application boundaries, exceptions, persistence ownership or repository-wide Java engineering needs design or review. - 90cc-c-project-standard
Use when Pure C module interfaces, ownership contracts, error-code cleanup paths, build conventions or C engineering validation need design or review. - 100cpp
Guides C++17/20/23 code: ownership and lifetimes, concurrency, CMake targets and ABI. Use when writing or reviewing .cpp/.hpp or CMakeLists.txt, chasing a dangling string_view or span, a coroutine or callback lifetime bug, atomic ordering, an ODR/ABI mismatch between targets, or a sanitizer report. - 90cpp-systems
Modern C++ patterns: RAII and ownership, rule of zero/five, exceptions and error handling, API and ABI boundaries, templates, and CMake tooling. Use when writing, reviewing, refactoring, or debugging C++, working with smart pointers, move semantics, memory leaks, template… - 100abi-stable
Migrate C++/CUDA PyTorch extension code to use the PyTorch stable ABI. Use when the user wants to make their project ABI stable, migrate to stable ABI, or use torch::stable APIs. - 90cpp-modern-systems
Use when writing or reviewing C++20/23 systems, libraries or performance-critical code. Implement robust modern C++ components with explicit ownership, numerical and concurrency semantics. Do not use when no C++ source or ABI is involved.