TsukiNi22/ai-utils / skills/routers/dev
dev
UnverifiedDevelopment 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 /dev: $ARGUMENTS
Single entry point: the user only invokes /dev (with or without a request) and Claude decides which skills
to use. Do not answer from this file: load the skills with the Skill tool first, then work.
1. Understand the request
The text given with /dev, otherwise the latest request of the user. With nothing at all: inspect the project
(step 2) and propose the next useful actions (uncommitted changes to commit, missing tests/docs, outdated
README/CHANGELOG, new libutils version...), without changing anything.
2. Inspect the context (in parallel, quick)
git status --short,git log --oneline -5,git remote -v.- Languages / build:
CMakeLists.txt,*.cpp/*.hpp(C++),package.json,pyproject.toml,Cargo.toml... - libutils:
find_package(utilsin the CMake orutils::in the sources. - Docs:
README.md,CHANGELOG.md,docs/.
3. Route
The category routers (cpp, python, setup-project, git, doc, style, legal, audit, and studio when
setup-studio generated it on this computer) are manual-only: don't call them with the Skill tool.
Read their decision table when the case is not obvious (<router>/SKILL.md), then load the
specific skills with the Skill tool:
| Need | Load (Skill tool) | Detailed table |
|---|---|---|
| new C++ project | cpp-project | cpp |
| C++ code, classes, main, architecture | cpp-class, cpp-style, cpp-comments | cpp |
| CMake, tests CMake, packaging | cmake-style | cpp |
| libutils APIs / exceptions | libutils, libutils-exception | cpp |
| install / update libutils on the computer, add it to the project | libutils-install, libutils-setup | cpp |
| unit tests (C++: GoogleTest like libutils) | cpp-tests (C++) or tests (any language, asks the framework) | cpp |
| test coverage: measure, what is not tested, fill it | coverage (C++, cpp-tests projects) | audit |
| performance: benchmark, profiling, what is slow, optimize | benchmark | audit |
| CI / CD, GitHub workflows, actions, Docker images of the CI | ci-cd | git |
| pre-commit hook (xstyle) | pre-commit | git |
compact a text / output for an AI, save tokens, add an --rtk mode to a program | rtk | - |
| choices / ideas / questions to ask the user ("propose en qcm", "demande-moi", several approaches) | interactive-questions | - |
| request unclear / ambiguous / incomplete, "clarifie", "vérifie que tu as compris", ask before acting | clarify (uses interactive-questions) | - |
| ideas, recommendations, an opinion on ideas, variants ("des idées ?", "ton avis", "améliore cette idée", brainstorm) | ideation (uses interactive-questions) | - |
| hand the work over to another session / machine / model ("export", "passation", "handoff", PASSATION.md) | export (uses rtk) | - |
| set up the context before working ("setup le contexte", read the repo and the old / archived sessions, load the useful skills / MCP) | setup-context (uses onboard when installed, interactive-questions) | - |
| no interruption until the end ("ne pose aucune question", "fais tout d'une traite", "pose tes questions à la fin") | ask-at-end (asks at the end with interactive-questions / ideation) | - |
| stop cleanly now and resume later ("stop tout proprement", "mets en pause", "on reprendra plus tard", /pause) | pause (checkpoint in ~/.claude/pauses) | - |
| resume a paused task ("continue", "reprends" after a pause, a checkpoint waiting for the project) | continue-work | - |
| write in the user's own voice ("écris comme moi", "avec mes mots", a message / note / prompt in his style) | write-like-me | - |
set up the context of a project / folder before working on it (read the repo, its git history, the earlier sessions that touched it: "onboard", "lis tout le repo", "prends connaissance du projet"; the project only, the skills / MCP of the session too: setup-context) | onboard (uses rtk) | - |
| make a presentation / slides / a deck / a PDF or PPT from a plan or an idea ("fais une présentation", "un ppt") | presentation (uses interactive-questions) | - |
| give every git / repository permission from the prompt ("tu as tous les droits", "commit/push sans demander", /full-permission) | full-permission | - |
| set up a whole new project (architecture + tests + license + git + CI/CD + README) | the steps of setup-project (its table, skills loaded in that order) | setup-project |
| several / all audits of the project at once | follow the audit router (checklist of audits + format) | audit |
| bugs / UB / crashes / sanitizers audit | audit-bugs | cpp |
| security audit, flaws, vulnerabilities, hacking, memory errors fixed until clean | audit-security | - |
| cleanliness / conventions audit with a PDF report | audit-quality | style |
| comments of any language, file headers | comments (+ cpp-comments) | doc |
| a deliverable as PDF (report, study, benchmark) | report | doc |
| license (choose, add, replace, compatibility) | license | legal |
| dependencies: licenses to credit / restrictive / paid, vulnerabilities | audit-deps | legal |
| legal compliance check: GDPR / RGPD, cookies, mentions légales, CGU, RGAA, privacy, erasure, AI Act, licenses and mentions | legal-check | legal |
| make it compliant: privacy policy, legal notice, cookie banner, terms, accessibility statement, data deletion / export | legal-setup | legal |
several languages / translate a project (multilingual-project) or a website (multilingual-website + multilingual-project) | multilingual-project, multilingual-website | - |
dark / light / system modes, themes, high contrast: a project (color-modes-project) or a website (color-modes-website + color-modes-project) | color-modes-project, color-modes-website | - |
| style only (format / review like the user) | cpp-style, cpp-comments, coding-style (other languages), cmake-style, comments by file type | style |
| Python code | python-style + python-comments | python |
| new Python class / module / tool / exception / test file | python-class | python |
| new Python project / package / tool | python-project | python |
| code in another language than C++ (shell, Lua, JS/TS, Rust, C...) | coding-style + comments | style |
| README, Markdown docs | readme-style | doc |
| GitHub wiki | wiki-style | doc |
| HTML docs, project graph | html-doc | doc |
| documentation site with search (claude-cluster docs style) | better-html-doc (+ better-explain-doc / better-protocol-doc for its explanation / protocol pages; one page in that look: better-html-style) | doc |
| explanation page (how something works), simple + technical | explain-doc | doc |
| protocol of a networking project (frames, handshake, codes, commands, storage) | protocol-doc | doc |
| any other HTML page, palette / color / font | html-style | doc |
| free space, deep clean: caches, old builds, downloads, duplicates, Docker, flatpak, dnf updates, old kernels, Claude Code / claude-cluster leftovers | computer-clean | - |
| set up / scan / refresh the creative tools (audio, image, video, 3D, simulation / VFX / rendering, their MCP servers) as skills | setup-studio (then /studio routes the creative requests) | - |
| a creative request: sound, music, voice, image, video, 3D model, simulation, render | the studio router when it was generated (/studio), else propose setup-studio | - |
| commit the current diff locally ("fais le commit") | git-commit | git |
| update every doc / site / wiki / package / install script after changes or a new version | docs-update | doc |
| commit message, branch, PR, tag, release, CHANGELOG | git-conventions | git |
| several needs (ex: "add the feature, document it and prepare the commit") | every matching skill, in the order of the work: code -> docs -> git | - |
| no skill matches (other language/tool) | none: say it, follow the conventions of the project | - |
4. Work
- Every audit, review, analysis or summary delivered to the user (including the "no request" state of the project)
goes through
report(format asked once: Markdown + PDF recommended / PDF / Markdown), English by default, inaudit/at the repository root unless asked; the chat only gives the verdict and the paths. - Follow the loaded skills strictly; they override generic habits.
- Never commit/push/tag/release/open a PR without an explicit request (
git-conventions). - Start the answer with one line:
Skills : <list> (<reason>), then do the task.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |