drupal-content-modeller--theme-ticket

Generate per-bundle Drupal theme tickets from live site introspection.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/richardgaunt/drupal-content-modeller --skill drupal-content-modeller-theme-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drupal-content-modeller--theme-ticket
Source: https://github.com/richardgaunt/drupal-content-modeller/tree/main/.claude/skills/drupal-content-modeller--theme-ticket
Command: npx skills add https://github.com/richardgaunt/drupal-content-modeller --skill drupal-content-modeller-theme-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates per-bundle Drupal theme tickets from live site introspection to guide frontend rendering decisions and keep frontend teams aligned with the content model.

Core Features & Use Cases

  • Produces a per-bundle Theme ticket that captures view modes, component bindings, text formats, and region placements based on live site introspection.
  • Aligns Theme tickets with existing BA tickets, ensuring tickets are created in the correct project path (projects/<slug>/tickets/) and sorted with their BA counterparts.
  • Helps frontend and design teams validate rendering decisions before Drupal YAML generation, reducing rework later in the pipeline.

Quick Start

Run the theme-ticket skill for your project after BA tickets are drafted to generate per-bundle theme tickets in projects/<slug>/tickets/.

Frequently Asked Questions about drupal-content-modeller--theme-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Drupal theme tickets for frontend rendering decisions?

You generate Drupal theme tickets by running live site introspection commands to capture per-bundle details like view modes, components, text formats, and region placements, then placing the output in projects/<slug>/tickets/.

When do I need to create per-bundle theme tickets in a Drupal project?

You need per-bundle theme tickets when BA tickets already exist and your frontend team requires specific rendering details such as view modes, component bindings, and region placements before proceeding to Drupal YAML generation.

What live introspection commands extract Drupal view modes and theme regions?

The skill uses commands including dcm view-mode, dcm component, dcm filter-list, dcm theme-regions, dcm theme-suggestions, and dcm theme-preprocesses to extract live site data for theme tickets.

Does this theme ticket generation require existing BA tickets to run?

Yes, this skill applies after BA tickets are drafted, aligning generated per-bundle theme tickets with existing BA counterparts in the correct project path to maintain frontend and content model alignment.

How do per-bundle theme tickets reduce frontend rework in Drupal?

Per-bundle theme tickets validate rendering decisions by capturing live component bindings and view modes before Drupal YAML generation, keeping frontend teams aligned with the content model and reducing later pipeline rework.

Can I use this skill without live Drupal site introspection?

No, this skill relies entirely on live site introspection commands to query actual view modes, components, text formats, and region placements, meaning it requires a running Drupal environment to generate accurate theme tickets.