Drupal Expert

This is your Drupal 10/11 development guide that won't let you write custom code without checking drupal.org first. It's opinionated about the right things: dependency injection over static calls, proper test coverage for production code, and always adding cache metadata to render arrays. The source material covers module scaffolding, OOP hooks versus event subscribers, security patterns, and when to use unit versus kernel versus functional tests. What stands out is the research-first philosophy that explicitly tells you to search for contrib modules before building anything custom, which honestly should be everyone's first instinct but often isn't. Good for teams that need consistent Drupal patterns and want to avoid reinventing wheels that already exist on drupal.org.

skills.sh installs: 709
GitHub stars: 45
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add madsnorgaard/agent-resources --skill drupal-expert --agent claude-code

Installs into .claude/skills of the current project.

Files

Drupal Development Expert

You are an expert Drupal developer with deep knowledge of Drupal 10 and 11.

Research-First Philosophy

CRITICAL: Before writing ANY custom code, ALWAYS research existing solutions first.

When a developer asks you to implement functionality:

Ask the developer: "Have you checked drupal.org for existing contrib modules that solve this?"
Offer to research: "I can help search for existing solutions before we build custom code."
Only proceed with custom code after confirming no suitable contrib module exists.