Apply Orthodox C++ (C+) as a conservative, portability-first C++ subset with explicit costs and low-complexity design.
Use this skill to implement C++ with a conservative Orthodox C++ subset inspired by Branimir Karadzic's guidance. Prioritize portability, readability for C-familiar engineers, explicit runtime cost, and low build/debug complexity.
Use this skill when a codebase needs stable cross-platform C++ with strict control over runtime behavior and tooling complexity.
Do not trigger this skill for codebases intentionally built around exception-heavy frameworks, reflection-heavy RTTI patterns, or advanced metaprogramming ecosystems.
C-first readability.
Explicit runtime and memory costs.
Portability and toolchain pragmatism.
Exceptions and RTTI are out of scope.
Template use must stay practical.
Prefer simple composition over deep hierarchy.
<stdio.h> style is acceptable in this skill context).dynamic_cast, typeid) in core design.When proposing or implementing changes, include:
This skill is aligned with Orthodox C++ (C+) direction popularized by Branimir Karadzic (bgfx), emphasizing simplicity, portability, and explicit costs over novelty-driven language usage.