Zivtech Drupal planner + critic + config executor for Claude Code github.com/zivtech/drupal-meta-skills
One Drupal architecture lane

drupal-meta-skills

A Zivtech-built consolidated workflow for Drupal teams that need architecture planning, deterministic config generation, and Drupal-specific review without splitting that work across separate repos or generic prompts.

Open Repository See Workflow
Planner

Design entity types, configuration schema, permissions, cache strategy, migration path, and theme implications before code.

Executor

Turn structured planner output into Drupal config YAML for the cases that should be generated deterministically.

Critic

Review implementation and generated artifacts for Drupal-specific risks generic review does not catch.

Planners
6+1

Main planner plus focused content-model, taxonomy, theme, canvas, and search sub-planners.

Review depth
9

Drupal-specific dimensions including security, architecture, operational safety, cache correctness, and editorial workflow.

Generation step
1

Config executor closes the gap between architecture intent and YAML artifacts for content model, taxonomy, and search specs.

Three lanes in one repo

This bundle exists because Drupal problems often begin in one phase and surface in another. A weak content model creates migration pain. A missing cache context looks fine until personalized output leaks. A config decision that seems local becomes a deploy problem later. This repo keeps those decisions in a single architecture lane.

Plan

/drupal-planner

  • Full 10-phase architecture planning for Drupal implementations.
  • Sub-planners for content model, taxonomy, theme, canvas, and search.
  • Contrib-first evaluation, permission mapping, cache strategy, migration path, and review checkpoints.
Generate

/drupal-config-executor

  • Consumes planner output and produces Drupal config YAML.
  • Best for content model, taxonomy, and search specs.
  • Acts as the deterministic bridge between design and review.
Review

/drupal-critic

  • Reviews Drupal implementations with domain-specific rigor.
  • Checks cache metadata, config workflow safety, contrib decisions, migration idempotency, and admin/editor impact.
  • Uses context-driven perspectives instead of generic review templates.

Workflow

  1. Run the main planner or the right sub-planner for the scope.
  2. Generate config YAML when the planner output is specific enough for deterministic execution.
  3. Implement the remaining project-aware code and integration work.
  4. Run the critic on the implementation or the generated artifacts.
  5. Refine with Drupal-specific evidence rather than broad code-review heuristics.

The 8-Step Accessibility Lifecycle

The a11y-critic serves at two checkpoints — after planning and after testing. This dual-review loop catches design-level accessibility gaps early and implementation-level regressions late, before they ship.

Planner Critic Manual Executor Test
  1. Plan a11y-planner Planner
  2. Critique Plan a11y-critic Critic Checkpoint 1
  3. Revise manual Manual
  4. Implement executor Executor
  5. Test a11y-test Test
  6. Critique Impl a11y-critic Critic Checkpoint 2
  7. Fix executor Executor
  8. Re-test a11y-test Test

Install

  1. Install the bundle with npx claude-skills for the fastest path.
  2. Manual install is also supported by copying root `.claude/skills` and `.claude/agents` into your Claude configuration.
  3. After installation, use the main planner, the relevant sub-planner, the config executor, and the critic as one workflow rather than as isolated prompts.
npx claude-skills add https://github.com/zivtech/drupal-meta-skills

# manual install
git clone https://github.com/zivtech/drupal-meta-skills.git
cp -r drupal-meta-skills/.claude/skills/* ~/.claude/skills/
cp drupal-meta-skills/.claude/agents/*.md ~/.claude/agents/

What this bundle is trying to prevent

Architecture debt discovered late

  • Entity type or field design that becomes migration work once content exists.
  • Permissions and workflow states left implicit until admin UX or moderation breaks.
  • Theme and render concerns postponed until preprocess logic becomes a dumping ground.

Operational bugs that generic review misses

  • Cache tags, contexts, or max-age that are almost correct and still wrong.
  • Config decisions that fail on deploy or drift across environments.
  • Custom code that duplicates contrib behavior without a justified reason.
  • Migration and update paths that are not idempotent or not rollback-safe.

Commands included

Planning

  • /drupal-planner
  • /drupal-planner.content-model
  • /drupal-planner.taxonomy
  • /drupal-planner.theme
  • /drupal-planner.canvas
  • /drupal-planner.search

Execution and review

  • /drupal-config-executor
  • /drupal-critic