cpp-classlisted
Install: claude install-skill TsukiNi22/ai-utils
# C++ files in Tsukini's style
`<name>` (a skill) = the folder of that skill: `~/.claude/skills/<name>` (setup.sh) or `${CLAUDE_SKILL_DIR}/../../*/<name>` (plugin of the marketplace).
Read before writing the first file:
- `reference/layout.md`: file/class layout, header, includes, attributes, **empty bodies rule**;
- the `cpp-style` skill (`SKILL_DIR/../cpp-style/SKILL.md`): naming, formatting, spacing;
- the `cpp-comments` skill (`SKILL_DIR/../cpp-comments/SKILL.md`): comments.
The files of `examples/` (real libutils code) are the ground truth for the layout.
`SKILL_DIR` below = the directory of this file.
## libutils freshness
First, once per conversation: the freshness check of the `libutils` skill (`bash <libutils skill>/scripts/check.sh`,
section "Freshness check" of `libutils/SKILL.md`). Outdated -> reuse the answer already given in this conversation,
else ask once (continue / update the installed libutils with `libutils-install` / the project's requirement with
`libutils-setup` / the skills reference) and remember it.
> **Architecture only: never write the content/logic of a function.** Every body is
> `/* Nothing */` (+ the minimal `return {};` when non-void), even if the user describes the
> behavior: it goes in a trailing comment of the declaration. The user writes the logic.
> Allowed: `= default`/`= delete`/`= 0`, init lists forwarding the parameters, one-member
> accessors, a public wrapper forwarding to its `name_` implementation. Details in `reference/layou