JMAILLY
UserClaude Code plugin: skills for migrating and modernizing Dockerized, Makefile-driven web projects — Drupal 10→11, PHP/Docker bumps, Gulp→Vite, Sass, jQuery 4, PHP_CodeSniffer.
Categories
Indexed Skills (8)
d11
Orchestrate the upgrade of a Dockerized, Makefile-driven Drupal 10 site to Drupal 11. Use when the user mentions a Drupal upgrade/migration, "D10 to D11", or wants the full campaign run in the correct order. Sequences three reusable sub-skills — php-docker-upgrade (PHP 8.4), php-deprecations-audit (upgrade_status/rector/phpstan), jquery-4-migration — around the D11-specific work it owns itself (module cleanup with deployable uninstall/purge update hooks, then a combined contrib + core bump + apply) and a per-step Git workflow (one Draft MR per step). IMPORTANT: fix deprecations BEFORE bumping core; pair every module removal with an uninstall hook so preprod/prod do not break on cim; all Drupal commands MUST go through Makefile targets.
gulp-to-vite
Migrate a Dockerized, Makefile-driven Drupal theme front build from Gulp to Vite. Use when the user mentions replacing Gulp with Vite, a "gulp to vite" migration, modernizing a Drupal theme build, dropping the gulp-* dependency tree, gulp-imagemin ARM/Alpine build pain, an `npm install` that fails on optipng-bin, or a Drupal theme whose SCSS/JS edits do not hot-reload. Covers the feasibility verdict, the plugin-to-disk (Arch B) approach that keeps *.libraries.yml untouched, ready-to-fork Vite plugins, the dev HMR wiring, the Drupal/Apache caching layers that must be disabled for HMR to work at all, and Docker/Makefile/CI changes. IMPORTANT: all build commands MUST go through Makefile/npm targets inside the node container, never run directly on the host.
jquery-4-migration
Migrate a Drupal theme's JavaScript from jQuery 3 to jQuery 4 (as shipped by Drupal 11), on a Dockerized Makefile-driven project. Use when the user mentions jQuery 3→4, jQuery 4 deprecated/removed APIs ($.trim, $.isFunction, $.isArray, $.type, .bind/.delegate…), a jquery-deprecated / migrate polyfill, or "$.x is not a function" after an upgrade. Covers scanning custom + contrib JS, native conversions, rebuilding assets, and a scoped local polyfill for not-yet-compatible third-party libraries. IMPORTANT: all builds MUST go through Makefile/npm targets, never on the host.
lando-to-docker
Migrate a Drupal project's local dev environment from Lando to Docker Compose + a Makefile (Traefik reverse proxy, *.dev.localhost, PHP-FPM + Apache, MariaDB, Redis, Adminer, Mailpit). Use when the user mentions replacing Lando, a ".lando.yml", "lando to docker", "lando to make", setting up the Makefile / Docker dev environment, or needs the Makefile that the d11 / gulp-to-vite / sass-migrator / php-docker-upgrade skills require. Produces the docker/ tree, docker-compose.yml, Makefile, and Drupal glue; handles single-site vs multisite and Gulp vs Vite/Tailwind frontends. IMPORTANT: after migration all commands MUST go through Makefile targets, never Lando or the host.
php-deprecations-audit
Audit and fix deprecated Drupal/PHP APIs in custom code before a major Drupal core bump, on a Dockerized Makefile-driven project. Use when the user mentions upgrade_status, drupal-rector, phpstan deprecation detection, "removed in D11" (or the next major) APIs, implicitly-nullable PHP 8.4 parameters, or fixing custom-code deprecations before bumping core. Runs upgrade_status + rector + phpstan, applies automatic + manual fixes, loops until 0 errors. IMPORTANT: all commands MUST go through Makefile targets; run this WHILE core is still on the OLD major, never after the bump.
php-docker-upgrade
Bump the PHP version of a Dockerized, Makefile-driven project (e.g. a Drupal site) to a target version — 8.4, 8.5 or later. Use when the user mentions upgrading PHP in Docker, changing the PHP base image / Dockerfile version, a "platform.php" constraint, or needs a newer PHP for a framework upgrade (e.g. PHP 8.4 required by Drupal 11). Covers locating the image, bumping it, rebuilding containers, verifying, and updating the Composer platform pin. IMPORTANT: all build commands MUST go through Makefile targets, never run directly on the host.
phpcs-standards
Set up or verify PHP_CodeSniffer on a Dockerized, Makefile-driven PHP project (Drupal or PSR-12), then bring the custom code to zero violations. Use when the user mentions phpcs, phpcbf, coding standards, "normes de codage", drupal/coder, DrupalPractice, PSR-12, a sniff, a ruleset / phpcs.xml, "FAILED TO FIX", or wants the custom modules cleaned up before a review or a major upgrade. Asks which standard (Drupal vs PSR-12) and which severity (errors only vs errors + warnings), fixes module by module, and records every behaviour-changing fix as a manual UAT step in the merge request. IMPORTANT: all commands MUST go through Makefile targets; phpcbf can discard every fix for a file silently, so a run is only clean when phpcs prints "No violations were found".
sass-migrator
Migrate a Dockerized, Makefile-driven Drupal theme's SCSS off deprecated Dart Sass syntax with sass-migrator, and clear the deprecation warnings at the source. Use when the user mentions sass-migrator, migrating @import to @use/@forward, the Sass module system, or Dart Sass deprecation warnings (mixed-decls, slash-div / division, strict-unary, legacy color functions). Covers the migrator run order, the fixes the migrator can NOT do (cross-file @extend, CSS max()/min() shims, mixed-decls source fixes), and a compiled-CSS non-regression harness that proves the output is unchanged. IMPORTANT: all builds MUST go through Makefile/npm targets inside the node container, never on the host.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.