Enforce a closed content inventory for generic artifacts. Use when creating, editing, planning, or reviewing PDFs, resumes, documents, slides, roadshows, videos, tutorials, web pages, generative images, or similar deliverables. Apply for artifacts by default unless the user explicitly requests detailed or comprehensive treatment.
Consult an independent read-only Claude Opus advisor when a decision can affect security, privacy, money, data loss, deployment, or public API compatibility; when investigation leaves two plausible directions with materially different consequences; or when a consequential completion claim depends on an unverified assumption or critical behavior that normal tests cannot cover. Also use when the user requests an independent or Opus review. Skip routine edits and uncertainty that local inspection, documentation, or tests can resolve cheaply. Opus challenges Codex's reasoning and evidence; Codex retains responsibility for edits and the final judgment.
High-quality C++ OOP coding style (archibate / parallel101 lineage) that overrides sloppy AI-default C++. Use this skill WHENEVER writing, editing, refactoring, or reviewing C++ code (.cpp / .h / .hpp / .cc / .cxx), designing C++ classes, interfaces, APIs, or libraries, or when the user mentions C++ design, OOP, design patterns, dependency injection, RAII, or "clean / modern C++". Also use it for CMake-first C++ project layout, module targets, usage requirements, third-party dependency acquisition and integration, binary ABI compatibility, installation, packaging, and application deployment. Apply it even when the user does not explicitly ask for a style: the default way models write C++ leans on free functions, public mutable state, raw new/delete, sentinel return codes, and long loose parameter lists — this skill replaces all of that with abstract-class-or-data-class design, dependency injection, type-rich APIs, value-based error handling, and RAII ownership.