dev
Skill1 starsChanged 3 days agoMITView on GitHub
Global development router - invoked manually with /dev, it inspects the request, the project and the languages involved, then loads the matching skills of the user (using the tables of the cpp, python, git, doc, style, audit and legal routers: cpp-project, cpp-class, python-project, python-class, python-style, python-comments, ci-cd, pre-commit, rtk, interactive-questions, clarify, coverage, benchmark, cpp-style, coding-style, cpp-comments, comments, cmake-style, cpp-tests, tests, audit-bugs, audit-quality, libutils, libutils-exception, libutils-install, libutils-setup, git-conventions, readme-style, wiki-style, html-doc, html-style, explain-doc, report, license, audit-deps) before doing the task.
55 other projects use a version of this.
Adopted by
Most recently taken up by
- waynesutton/convexskillstheir own version, first seen Nov 15, 2026
- waynesutton/builder-skillstheir own version, first seen Nov 15, 2026
- ztcools/skillstheir own version, first seen Nov 15, 2026
- mayoz/rabbittheir own version, first seen Nov 15, 2026
- DataArt/artisyn-implementation-harnesstheir own version, first seen Nov 15, 2026
- inancgumus/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use metrics-graphana, control-flow and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
slopusSkillmetrics-graphana
Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.
Also in 3 projects that use this
slopusSkillcontrol-flow
Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.
Also in 3 projects that use this
MicrosoftSkillsessions
Core principles and workflow router for changes to the Agents Window under src/vs/sessions.
Also in 3 projects that use this
AnthropicSkilloffice-hours
Set up and run Claude Code office hours, including the calendar event when the champion's own calendar connector allows it. Use when a champion wants a regular time for teammates to bring problems.
Also in 3 projects that use this
nicepkgSkillteam
根据任务快速组建临时 AI Agent 团队协作。自动从 .claude/agents/ 中选择最合适的成员组队。
Also in 3 projects that use this
Microsoft AzureSkilltest
Also in 5 projects that use this
Other versions55 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 55
- slopus/happy★ 25ksame name
- microsoft/playwright-cli★ 15ksame name
- atopile/atopile★ 4ksame name
- cexll/myclaude★ 2.8ksame name
- waynesutton/markdown-site★ 628same name
- Automattic/wordpress-activitypub★ 583same name
- waynesutton/builder-skills★ 404same name
- waynesutton/convexskills★ 404same name
- justrach/merjs★ 357same name
- stella/stella★ 274same name
45 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- write-like-meSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 37 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 94
Every audit, review, analysis or summary delivered to the user (including the "no request" state of the project) goes through report …
- Distinctive: line 97
Follow the loaded skills strictly.
- Very specific: line 98
Never commit/push/tag/release/open a PR without an explicit request (git-conventions).
- Very specific: line 99
Start the answer with one line: Skills : <list> (<reason>), then do the task.
“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Development 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) 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: caches, Docker, old builds, 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

