Theodorosploumis Drupal Best Practices
theodorosploumis-drupal-best-practices is a Claude Code plugin for the Build phase that steers Drupal module, entity, Views, caching, and theming work toward a short list of enforced best practices.
by theodorosploumis · github.com/theodorosploumis/drupal-best-practices
Keep Drupal modules, entities, Views, caching, and theming aligned with opinionated conventions while an agent scaffolds or refactors a site.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install theodorosploumis-drupal-best-practices@theodorosploumis/drupal-best-practicesBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:theodorosploumis/drupal-best-practices") and the paste-ready config with skillselion.get_install_config("plugin:theodorosploumis/drupal-best-practices").
What it does
theodorosploumis-drupal-best-practices is a Claude Code plugin bundle that packages a short, opinionated checklist of Drupal conventions for solo builders and small teams shipping CMS-backed products. It targets agents and developers who need disciplined answers when creating custom modules, defining entities and fields, configuring Views and taxonomy, handling forms and text formats, and aligning theme templates with display modes. Rather than replacing Drupal docs, it compresses recurring decisions—caching, security settings, asset handling, config export, and frontend preprocessing—into patterns an agent can apply consistently across a codebase. Install it when you are building or extending Drupal sites and want fewer one-off implementations, clearer naming, and validation-aware entity work. It matters because Drupal’s flexibility makes inconsistency expensive; this kit steers implementation toward maintainable, editor-friendly, production-shaped structure from the first scaffold.
Highlights
- 10-plugin bundle covering modules, entities, fields, Views, taxonomy, and config management
- Opinionated guidance on caching, security, validation, and performance optimization for Drupal
- Theme, template, preprocessing, and responsive display patterns for editors and frontend
- Naming, storage, and export conventions for reusable blocks, formats, and custom functionality
- Content-type, vocabulary, and display-mode planning without ad-hoc structure drift
Why builders use it
Drupal projects sprawl into inconsistent modules, fields, Views, and theme code because agents lack a compact, opinionated rule set for CMS architecture.
After you add the plugin, agent-generated Drupal changes follow shared conventions for entities, config, performance, security, and displays instead of one-off patterns.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 34 stars, 0 votes.
FAQ
Who is theodorosploumis-drupal-best-practices for?
It is for developers and AI-assisted workflows on Drupal who need consistent module, entity, View, and theme patterns without rereading lengthy core documentation each session.
When should I use theodorosploumis-drupal-best-practices?
Use it during Drupal feature work, refactors, and launch prep whenever you want caching, security, config export, and content modeling handled with the same opinionated checklist.
How do I add theodorosploumis-drupal-best-practices to my agent?
Install the plugin from the theodorosploumis/drupal-best-practices Claude Code plugin bundle, enable it in your Claude Code project, and invoke it when editing Drupal modules, entities, or themes.
Comments
Share how you use theodorosploumis-drupal-best-practices, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.