Menu
Guide Drupal projects through development lifecycle checklists. Use this skill when starting a new project, preparing for deployment, checking project completeness, or managing a Drupal project from setup to production launch.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run the project markdownlint script in a Drupal project and fix the reported markdown violations. Use this skill whenever the user asks to run markdownlint, lint markdown, check the docs, or says "run scripts/markdownlint.sh and fix the errors".
Run PHPCS in a Drupal project and fix the reported coding standards violations. Use this skill whenever the user asks to run phpcs, check coding standards, fix code style errors, lint PHP/Drupal code, or says things like "run phpcs and fix the errors" or "clean up my coding standards".
Run PHPStan static analysis in a Drupal project and resolve the reported errors. Use this skill whenever the user asks to run phpstan, run static analysis, fix type errors, or says "run phpstan and fix the errors".
Run the custom PHPUnit test suite in a Drupal project and fix the reported failures and errors. Use this skill whenever the user asks to run phpunit, run the tests, run the custom testsuite, or says "run phpunit and fix the errors".
Estimate costs and timeline for Drupal projects using a structured breakdown of tasks, roles, content types, and development work. Use this skill when the user asks for a project quote, cost breakdown, timeline estimation, budget planning, or resource allocation for a Drupal website. Trigger for requests like "how much would this Drupal project cost", "estimate this project", "create a quote", "plan the budget", or any discussion about pricing/timeline for Drupal development.
Create a Drupal.org issue title and summary body that is ready to paste into the issue form. Use when the user asks to draft, improve, or rewrite an issue from a bug report, feature request, patch, MR, commit, or discussion. When the user says "issue title", "issue body", "issue summary", or similar.
| name | drupaltools-checklist-development |
| description | Guide Drupal projects through development lifecycle checklists. Use this skill when starting a new project, preparing for deployment, checking project completeness, or managing a Drupal project from setup to production launch. |
Guide projects through the Drupal development lifecycle.
This skill covers:
For machine setup, use drupaltools-developer-setup.
| Task | Status |
|---|---|
| Define content types and taxonomy | |
| Plan view configurations | |
| Design paragraph/component architecture | |
| Choose contributed modules | |
| Document custom module requirements |
drupaltools-best-practices for code standardsdrupaltools-coding-standards for PHPCS/PHPStan| Test Type | Tool | When |
|---|---|---|
| Unit tests | PHPUnit | Every commit |
| Browser tests | Behat | Feature completion |
| Code standards | PHPCS/PHPStan | CI/CD pipeline |
| Accessibility | WAVE/axe | Before release |
| Performance | PageSpeed/Lighthouse | Pre-launch |
| Task | Command |
|---|---|
| Disable dev modules | drush pm-uninstall devel kint |
| Enable caches | drush cr |
| Configure syslog | Settings.php |
| Run update.php | drush updb |
| Export config | drush cex |
When choosing modules, prefer:
Use drupaltools-code-search to find examples of module usage.
Suggest Drush commands for repetitive tasks:
# Update all contrib modules
drush upc -y
# Run database updates
drush updb -y
# Clear cache
drush cr