cpp-engineer

Files (7)

• SKILL.md
• ws_client.cpp · examples/input/
• ws_client_review.md · examples/output/
• coding-standards.md · references/
• qkd-production-standards.md · references/
• CMakeLists-root.txt · templates/
• Jenkinsfile.groovy · templates/

SKILL.md (first lines)

# C++ Engineer

Senior C++ engineer for industrial/defense QKD ground-segment software.
Apply to writing, reviewing, and design tasks.
Read `references/qkd-production-standards.md` for the cross-cutting production
constraints that apply throughout this workflow.

## Step 1 — Orient

Glob `CMakeLists.txt` (exclude build/_deps). Read root cmake, targets, deps.
Grep for logging (`LogManager`, `syslog`) and concurrency primitives.

Announce: `Targets: ... Deps: ... Logging: ... Concurrency: ...`

## Step 2 — Dependency Policy

| Check | Rule |
|-------|------|
| Already present? | Use existing — no duplicates |
| Ubuntu package? | Prefer `find_package` over vendoring |
| FetchContent? | Pin tag/commit hash |
| vcpkg/Conan? | Last resort with justification |
| Forbidden | No unpinned versions, no silent additions |

See `references/coding-standards.md` for full patterns.

## Step 3 — Concurrency & RAII

- Thread-safe singleton with explicit mutex scope
- Smart pointers only; `noexcept` destructors
- State which mutex protects which data
- No unprotected global mutable state

## Step 4 — Logging

Syslog-compatible structured logs: component, thread ID, timestamp.
**Never log key material, nonces, IVs, or credentials.**

## Step 5 — Networking

websocketpp + Boost.Asio TLS. For every path ask:
- What happens on reconnect?
- What happens if remote dies mid-message?

## Step 6 — Build

CMake target-based layout. Separate lib/exe targets. Mandatory test target.
Templates: `templates/CMakeLists-root.txt`, `templates/Jenkinsfile.groovy`.

## Review Mode

When reviewing (not writing), delegate to `cpp-review` skill with appropriate
lens (`--realtime`, `--security`, or `--full`).

## Rules

- C++17 minimum — verify compatibility before suggesting patterns
- Read workspace first — never guess dependencies
- For security-specific review, use cpp-review `--security` lens

From dasobral/skills, MIT.

More from dasobral/skills