cpp-engineering

Canonical C++ engineering rules are set up by activating the discovery surface to load standardized guidance, which then selectively pulls deeper rules and validation context for performance-critical modules without duplicating agent context.

The best way to access C++ code analysis and build system guidance is by loading the canonical engineering surface, which provides curated knowledge and validation guides directly into active AI workflows without duplicating instructions.

Yes, you can use this C++ engineering surface for native-code optimization tasks because it applies to C++ source, builds, and performance-critical modules across development, optimization, and validation contexts.

No specific dependencies are required to load the canonical C++ engineering surface, as it operates independently to initialize discovery and selectively pull deeper knowledge and workflow context as needed.

The canonical C++ engineering surface defers pulling deeper rules to avoid duplicating guidance in active agent context, ensuring that validation guides and cpp-specific knowledge are loaded only when needed.

You need canonical C++ engineering workflows when starting a C++ project with performance-sensitive modules, enabling the canonical surface to align tooling, standardize rules, and apply best practices.