claude-migration-skills
CLAUDE.md0 starsChanged 24 days agoMITView on GitHub
This repository is public. Never mention any real project, client, site, agency, internal host or ticket/MR number in anything committed or published: skill files, references, templates, README, CHANGELOG, commit messages, tags, GitHub release notes. - Refer to a real-world run generically: "Project A", "a client project", "one reference project". Keep the lesson, drop the origin. - Use placeholders for hosts and identifiers (gitlab.example.com, my_theme, my_module). - Before every commit and release, check the diff, the message and the notes for…
In this repository17 other files it gives its agents.
- d11Skill
- drupal-build-foundationsSkill
- drupal-build-intakeSkill
- drupal-buildSkill
- drupal-build-unitSkill
- drupal-rgaaSkill
- drupal-scaffoldSkill
- gulp-to-viteSkill
- jquery-4-migrationSkill
- lando-to-dockerSkill
- phpcbfSkill
- phpcsSkill
- php-deprecations-auditSkill
- php-docker-upgradeSkill
- php-standardsSkill
- phpstanSkill
- sass-migratorSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use placeholders for hosts and identifiers (gitlab.example.com, my_theme, my_module).
- Very specific: line 14
Before every commit and release, check the diff, the message and the notes for names of local projects (directories under …
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repository rules
No real project names — ever
This repository is public. Never mention any real project, client, site, agency, internal host or ticket/MR number in anything committed or published: skill files, references, templates, README, CHANGELOG, commit messages, tags, GitHub release notes.
- Refer to a real-world run generically: "Project A", "a client project", "one reference project". Keep the lesson, drop the origin.
- Use placeholders for hosts and identifiers (
gitlab.example.com,my_theme,my_module). - Before every commit and release, check the diff, the message and the notes
for names of local projects (directories under
~/Documents/projects/). The localpre-commit/commit-msghooks enforce this.
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.