How do I install the PHP Drupal Engineering Profile skill?

Run npx skillmds@latest add jovanipink/php-drupal-engineering-profile in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is PHP Drupal Engineering Profile safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with PHP Drupal Engineering Profile?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is PHP Drupal Engineering Profile free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published PHP Drupal Engineering Profile?

JovaniPink (@jovanipink) published this skill. Their other Agent Skills are listed on their SkillMD profile.

PHP Drupal Engineering Profile by jovanipink

Name: PHP Drupal Engineering Profile
Author: JovaniPink

PHP Drupal Engineering Profile

Apply focused PHP and Drupal engineering judgment after repository gate discovery. Use for Composer projects, Drupal modules or themes, entity and configuration APIs, caching, security, tests, compatibility, and builds; defer exact commands to repository evidence.

JovaniPink 372c426 3 files · 4.1 KB Updated Sep 17, 2026

File contents

PHP and Drupal Engineering Profile

Use this profile only after repository discovery identifies the stack. Read focused checks when PHP- or Drupal-specific gates or hazards determine the result.

Workflow

Discover Composer metadata and lockfiles, PHP constraints, Drupal core version, custom modules or themes, configuration synchronization paths, service definitions, routes, update hooks, frontend manifests, and repository scripts.
Follow repository-defined commands, local development tooling, and pinned PHP, Composer, and Drupal versions before suggesting defaults.
Review material PHP hazards, especially type coercion, loose comparisons, nullability, error handling, user-controlled input, output encoding, deserialization, filesystem access, sessions, and environment-specific configuration.
Review Drupal-specific boundaries: access checks, entity queries, render arrays, cache tags and contexts, configuration versus state versus content, service lifetimes, plugins, update paths, queues, and request-scoped behavior.
Select proportionate gates from repository formatting, static analysis, coding standards, unit, kernel, functional, browser, frontend, dependency, and build checks.
Review compatibility across PHP and Drupal core versions, Composer constraints, contributed modules, database drivers, configuration schema, cache behavior, API deprecations, and content update order.
Report every missing tool, skipped command, unavailable database, or unsupported runtime as incomplete rather than passing.

Boundaries

Do not assume a global Composer, Drush, PHP, database, or local-environment command when the repository defines its own tooling.
Do not install modules, update the lockfile, import configuration, run update hooks, alter content, deploy, or mutate shared state merely to run a gate.
Separate static review, executed checks, local-site behavior, configuration import evidence, deployment, and live behavior.

Output

Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.

---name: php-drupal-engineering-profiledescription: Apply focused PHP and Drupal engineering judgment after repository gate discovery. Use for Composer projects, Drupal modules or themes, entity and configuration APIs, caching, security, tests, compatibility, and builds; defer exact commands to repository evidence.license: MIT---# PHP and Drupal Engineering ProfileUse this profile only after repository discovery identifies the stack. Read [focused checks](references/checks.md) when PHP- or Drupal-specific gates or hazards determine the result.## Workflow1. Discover Composer metadata and lockfiles, PHP constraints, Drupal core version, custom modules or themes, configuration synchronization paths, service definitions, routes, update hooks, frontend manifests, and repository scripts.2. Follow repository-defined commands, local development tooling, and pinned PHP, Composer, and Drupal versions before suggesting defaults.3. Review material PHP hazards, especially type coercion, loose comparisons, nullability, error handling, user-controlled input, output encoding, deserialization, filesystem access, sessions, and environment-specific configuration.4. Review Drupal-specific boundaries: access checks, entity queries, render arrays, cache tags and contexts, configuration versus state versus content, service lifetimes, plugins, update paths, queues, and request-scoped behavior.5. Select proportionate gates from repository formatting, static analysis, coding standards, unit, kernel, functional, browser, frontend, dependency, and build checks.6. Review compatibility across PHP and Drupal core versions, Composer constraints, contributed modules, database drivers, configuration schema, cache behavior, API deprecations, and content update order.7. Report every missing tool, skipped command, unavailable database, or unsupported runtime as incomplete rather than passing.## Boundaries- Do not assume a global Composer, Drush, PHP, database, or local-environment command when the repository defines its own tooling.- Do not install modules, update the lockfile, import configuration, run update hooks, alter content, deploy, or mutate shared state merely to run a gate.- Separate static review, executed checks, local-site behavior, configuration import evidence, deployment, and live behavior.## OutputReturn Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.

Frequently asked questions