Use when creating or extending Drupal 11 custom modules, including scaffolding, service architecture, and dependency injection best practices.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add siva01c/claude-plugins --skill drupal-module-development --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Drupal Module Development?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/siva01c-drupal-module-development)More formats (shields.io, HTML) on the badges page.
---
name: drupal-module-development
description: Use when creating or extending Drupal 11 custom modules, including scaffolding, service architecture, and dependency injection best practices.
---
# Drupal Module Development Skill
## Purpose
Use this skill when creating or extending custom Drupal 11 modules with modern architecture and maintainable code.
## When to apply
- Building a new custom module in `web/modules/custom`.
- Adding services, event subscribers, forms, or controllers.
- Refactoring procedural logic to service-based design.
## Workflow
1. Scaffold the module structure (`.info.yml`, `.services.yml`, routing, permissions).
2. Register dependencies through service definitions and constructor injection.
3. Build controllers/forms/plugins using Drupal 11 APIs and strict typing.
4. Add config schema for any custom configuration.
5. Validate with Drush cache rebuild and config export.
## Guardrails
- Avoid direct use of superglobals in business logic.
- Prefer dependency injection over static service locators.
- Keep schema, permissions, routes, and services documented and versioned.
- Do not modify Drupal core or contrib module code directly.
## Quick command checklist
```bash
drush en <module_name> -y
drush cr
drush config:export -y
```
In a containerized environment, prefix with your runner (e.g. `ddev drush …` — see the `ddev-tools` plugin).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.