← ClaudeAtlas

libutils-setuplisted

Set up libutils in the current C++ project - find_package(utils X.Y.Z) with the installed version, utils::utils on every target, and optionally the custom exception codes (JSON config, generator scripts, CMake generation block, include/exception, .gitignore) - in the user's CMake layout, installing libutils first when it is missing; libutils v4 (no v3 names), its Windows build too (MinGW-w64). Use whenever the user wants to add/use libutils in an existing project, link it in the CMake, or set up custom libutils exceptions in a repository.
TsukiNi22/ai-utils · ★ 1 · Web & Frontend · score 74
Install: claude install-skill TsukiNi22/ai-utils
# libutils in the current project `<name>` (a skill) = the folder of that skill: `~/.claude/skills/<name>` (setup.sh) or `${CLAUDE_SKILL_DIR}/../../*/<name>` (plugin of the marketplace). ## 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. `SKILL_DIR` = the directory of this file. ## 1. Is libutils installed? ```bash bash <libutils-install>/scripts/libutils.sh status ``` Not installed (or older than needed) -> **libutils-install** skill (`libutils.sh install`, last version through `libutils-pre`; root needed: give the user the command to run with `! `), then come back. A `/usr/local` source install shadowing the packages is reported: tell the user (it decides which version compiles). ## 2. Set it up ```bash python3 SKILL_DIR/scripts/setup_project.py <project root> [--exceptions] [--targets a,b] [--version X.Y.Z] [--dry-run] ``` Run it with `--dry-run` first when the CMake isn't in the user's layout, show the diff, then for real. Idempotent (a second run changes nothing). In the `cmake-style` sections (created when missing): - `# Requirement`: `find_package(utils <installed version> CONFIG REQUIRED) # Chec