Adopting AI can feel overwhelming, so I am sharing a few tales from my experience creating, maintaining, and assisting with contributed Drupal modules. AI can do a decent job of building a "greenfield" Drupal module from scratch, so my first tale is about using AI to build and contribute a module. For my next tale, I want to talk about using AI to maintain an existing "brownfield" Drupal module and to explore what is possible with AI.

Do you fall into the AI-possible camp, the AI-cautious camp, or somewhere in between?

I started experimenting with one of the most popular agent skills, /grill-me by Matt Pocock, which proved to be a game-changer.

What’s your take on the /grill-me skill? Do you see /grill-me as a game-changer for working with AI and Drupal to learn new things and solve challenging problems?

Where are you in your AI journey when it comes to building a Drupal module? Have you tried it? Are you ready to try it? Would you contribute an AI-generated module back to Drupal?

I'm going to tell three tales about building, maintaining, and contributing to different Drupal modules. My first tale is about using AI to build and contribute to a module. My second tale will be about maintaining a module. My last tale will be about contributing to someone else's module.

Everyone using the Webform module for Drupal should update to the latest version to mitigate 20+ security vulnerabilities.

AI has made it easier to find and exploit security vulnerabilities, while also making it easier to organize, review, and fix security issues. As the maintainer of the Webform module, I felt it was time to address all known Webform security issues, using Codex to organize, test, and assist with each one. I found AI to be the most effective way to address issues that had been unresolved for four years. The experience felt like using AI to hammer at the Webform module's security issues.

AI can be stubborn and frustrating. Can Drupal become an AI harness that steers humans and AI, both inside and outside Drupal, toward success, without Drupal losing its openness, stability, and scalability?

I know this blog post's title implies losing my (programming) skills, and I will gladly address my feelings about how agentic coding has caused my problem-solving and coding to atrophy from lack of use. The main focus of this post is about losing, specifically deleting, my overly verbose and complicated skills and AGENTS.md files.

Do you feel you are losing your coding skills when working with a coding agent, or do you see other skills emerging as you experiment with AI?

I was starting to feel weighed down by token and cost anxiety, but everything shifted when OpenAI cut the price of GPT 5.6 Luna by 80%. This dramatic drop in cost per token completely transformed how I choose and use models for Drupal development.

Think of AI as the new kids on the block/team you onboard every morning and offboard at the end of the day.

https://www.jrockowitz.com/blog/vibing-drupal-new-kids-on-the-block

See how I start with the statement "AI is making great programmers even greater and not-so-great programmers, well, not-so-great" and somehow end up concluding that everyone needs to be open to "vibe coding" with Drupal.

AIs are eating our websites, and we need to adapt by bringing AI into our website to enhance our content and user experience and provide a five-star dining experience.

I recently released a module called the AI Schema.org JSON-LD module, which I built with AI in 4 days. It replaces a key part of my Schema.org Blueprints module that I worked on for 4 years. AI ate my work, and I need to be okay with that.

Learn about my new AI Schema.org JSON-LD module, which generates structured data to "feed the machines"

I am continually experiencing both successes and failures while playing in my Drupal (AI) playground. I decided to keep things useful, simple, and achievable by building a Plugin Report module using AI.

I am continually experiencing both successes and failures while playing in my Drupal (AI) playground. I decided to keep things useful, simple, and achievable by building a Plugin Report module using AI.

Wednesday, April 8 @ 12:30 PM - 1:30 PM EDT - Virtual

I think we are seeing the beginnings of a Drupal AI developer experience initiative. I am looking forward to attending.

Learn about my experience building a module and contributing back to Drupal using Claude Code and OpenAI's Codex.

Learn how installing some Drupal-specific skills increased Claude Code's reliability when 'clauding' in my Drupal (AI) Playground.

I am starting to explore how to incorporate AI into my Drupal development workflow by creating a Drupal (AI) Playground. My first step was to bake some installation recipes, but it did not go as planned.