cpplisted
Install: claude install-skill TsukiNi22/ai-utils
# C++ router
`<name>` (a skill) = the folder of that skill: `~/.claude/skills/<name>` (setup.sh) or `${CLAUDE_SKILL_DIR}/../../*/<name>` (plugin of the marketplace).
**Request given with `/cpp`:** $ARGUMENTS
Do not answer from this file: decide which skills apply, **load them with the Skill tool** (never the other routers: they are manual-only), then do the task
following them. The request is the text given with `/cpp` (or, if empty, the latest request of the user;
if there is none, inspect the project and propose what can be done).
## 1. Look at the context (quickly, in parallel)
- `CMakeLists.txt`, `include/`, `src/`, `tests/`, `cmake/config/exceptions/` present? Empty folder = new project.
- libutils used? `bash <cpp-class>/scripts/detect_libutils.sh <root>` (`internal` / `libutils` / `std`),
`grep -rl "utils::" src include`.
- Files the request is about (open them before deciding).
## 2. Pick the skills (several can apply, load all of them before writing)
| Situation | Skills |
|---|---|
| new project / repository / "setup" | `cpp-project` (it loads the others it needs) |
| new class, interface, abstract, struct, enum, module, main, architecture | `cpp-class` (+ `cpp-style`, `cpp-comments`) |
| write / edit / refactor / fix C++ code | `cpp-style` + `cpp-comments` (+ `libutils` if the project uses it) |
| comments only | `cpp-comments` (`comments` for CMake/shell/other files of the project) |
| review C++ code against the user's style | `cpp-style` + `cpp-comments`