Theme development and frontend best practices for Drupal. Provides guidance on creating themes, using Twig templates, theme preprocessing, asset management, and responsive design in Drupal.

GitHub stars
35

Install

/plugin install drupal-theming@drupal-best-practices

Run it inside Claude Code after adding the marketplace with /plugin marketplace add theodorosploumis/drupal-best-practices.

Contents

Discovered from source

Skills 1

Description

Guide Claude to create themes that favor Twig, preprocess logic, and atomic SCSS structure while keeping overrides minimal and purposeful.

Usage

  • Ask for one-word machine names without theme or base-theme prefixes.
  • Request guidance on using Classy as a base theme and limiting overrides to documented needs (404/403/maintenance/login, etc.).
  • Have Claude propose SCSS structure by responsibility (variables, mixins, entities, components) and class naming (twig-, js-).

Guardrails

  • Avoid path-based styling; add classes in preprocess, not templates.
  • Prefer Twig templates with minimal logic; do not overuse theme overrides.
  • Use semantic class prefixes and comment mixins/functions; keep SCSS split by responsibility.

Validation

./ai/scripts/validate-theming.sh

References

  • Drupal Best Practices README.
  • Use Classy as a base theme; keep machine names one word and human-readable.

Sponsors

Details

Marketplace
theodorosploumis/drupal-best-practices
Source
ai/skills/theming
Category
Community

More from theodorosploumis/drupal-best-practices

All 10