Skip to content
Back to skills

Cc Cpp Project Standard

ASecurity

Use when C++ module/header boundaries, resource lifetime, exception safety, ABI, build-standard conventions or project-wide C++ checks need design or review.

  • 23 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 12, 2026
developmentc++frontendbackend

Works with

  • cli

Security analysis

A100/100

Pro scans all 10 files and shows the line behind each finding

Scanned November 12, 2026

npx -y skills add bovinphang/frontend-craft --skill cc-cpp-project-standard --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cc Cpp Project Standard?

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

Security grade badge for Cc Cpp Project Standard
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bovinphang-cc-cpp-project-standard-frontend-craft/badge)](https://www.skillsdirectory.com/skills/bovinphang-cc-cpp-project-standard-frontend-craft)

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: 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 skill

  • SKILL.md1.5 KB
  • examples/engineering/README.md1.3 KB
  • examples/engineering/boundary.cpp915 B
  • examples/engineering/boundary.hpp485 B
  • examples/engineering/boundary_test.cpp1.9 KB
  • references/common/engineering-practices.md12 KB
  • references/common/engineering-practices.rules.json2.2 KB
  • references/common/engineering-practices.sources.json15.9 KB
  • references/engineering-practices.md4.8 KB
  • references/practice.md1.9 KB

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.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.