C++ coding conventions. Use when editing .cpp/.hpp files or asking about C++ style.
Enforces C++ coding conventions including west const, auto usage, and class structure when editing .cpp/.hpp files. Applies clang-format and clang-tidy rules from repository config files.
/plugin marketplace add tenzir/claude-plugins/plugin install cpp@tenzirThis skill inherits all available tools. When active, it can use any tool Claude has access to.
naming.mdUse clang-format for formatting and clang-tidy for linting. The .clang-format
and .clang-tidy files in the repository root are authoritative—run the tools
and trust the output.
These are not enforced by tooling:
const T& not T const&auto: Use almost-always-auto, make conversions explicit (e.g., auto x = int64_t{0}).hpp, implementation: .cpp<module>/fwd.hpp#pragma once—no manual include guardsMember order:
public, then protected, then privateRules:
explicitexplicit(false) when implicit conversion is intentionalnoexceptstruct for simple data aggregates where the public members are the APIclass for template parameters; typename only for dependent typesT, packs Ts, arguments x, packs xs*_t and *_v helpers for traitsFIXME: for bugs, TODO: for improvements (colon required)/// with Markdown—do not use @param, @returns, @pre, @postThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.