DrupalCon Chicago 2026: How I vibe-coded my first custom Drupal module extending CKEditor

I was at DrupalCon Chicago 2026 , juggling booth duty, an AI Summit talk, and a Lightning Talk about CKEditor's contrib modules. But it's those hallway conversations that stick with you – and this time, the same question kept coming up. "How do I customize CKEditor just a little bit?" "Can I add my own button?" "I want something specific to our workflow, but where do I even start?" People knew what they wanted. They just didn't know how to get there. So I grabbed Wojtek Kukowski – the main maintainer of the CKEditor Drupal modules ( CKEditor 5 Plugin Pack and CKEditor 5 Premium Features ), and asked him: "What's actually required to make a CKEditor plugin extension for Drupal?" He briefed me on the essentials: create a Drupal module that wraps a CKEditor plugin. And I thought: "Let me try to translate this into a prompt for Claude Code and include the official docs and see what happens." The experiment Setup Drupal : 11.3.3. Tool : Claude Code. Goal : Create a Drupal module with a CKEd