Skills for Working with AI Agents in TYPO3 Projects

My popular TYPO3 Skills Collection has grown into a fairly extensive collection over time. While this was helpful, it eventually became confusing: skills for site packages, extension development, and large-scale migrations were all bundled together in a single package.

In addition, the Agent Plugins v1.0.0 standard has now been adopted, which simplifies the installation of skills, provided that the agent or AI harness being used already supports this standard.

The new TYPO3 Skill Plugins replace and reorganize my collection of skills. The TYPO3 Integrator Plugin is particularly helpful for integrators and in day-to-day project work. Topics that are only relevant when developing your own extensions now have their own package. The same applies to upgrades and migrations.

For example, you no longer need to load the migration modules when working on a project with the current TYPO3 version. Conversely, however, the TYPO3 Integrator Plugin remains the sensible starting point for virtually every TYPO3 project.

A skill provides an AI agent with specific work instructions and TYPO3 context for a task. Instead of having to explain how a Site Package, TypoScript, TCA, or DDEV project works every time a request is made, the agent is provided with the appropriate technical knowledge and a practical workflow. In addition, AI models are often trained using outdated TYPO3 documentation and TYPO3 code, which frequently leads them to produce outdated results and incorrect “solutions.” My skills provide the AI models with “up-to-date” information on how TYPO3 currently works.

The Integrator Plugin as a Common Foundation

The TYPO3 Integrator Plugin is intended for anyone working on TYPO3 projects. So it’s not just for traditional integrators, but explicitly also for extension developers and for people who are currently preparing for or carrying out an upgrade.

It includes more than 20 skills (as of Sept. 2026) for tasks that come up repeatedly in many projects: Fluid templates, navigation, route enhancers, content blocks, site sets, CKEditor, forms, structured data, XML sitemaps, Content Security Policy, DDEV worktrees, Playwright tests, and deployments.

Whether you want to create a new Fluid template, implement a language menu cleanly, or keep a form configuration maintainable, the Integrator plugin is the right foundation. These issues remain relevant even when developing a new extension or performing an upgrade. The new Extbase plugin is of little help if the surrounding site package is unclear.

For Your Own TYPO3 Extensions

The TYPO3 Extension Developer Plugin is designed for developers building frontend or backend extensions for TYPO3 v13 and v14.

It bundles skills for Extbase plugins, FlexForms, Scheduler tasks, and extension translations. These are tasks where an AI agent with no TYPO3 experience can quickly generate code that looks plausible at first glance but doesn’t integrate cleanly into TYPO3.

The Extbase skill, for example, helps you think about models, repositories, controllers, TCA, TypoScript, and Fluid templates as a unified whole. The FlexForm skill handles current XML definitions and cleans up legacy code as needed. For Scheduler Tasks or translatable custom records, context is just as important because data management and backend configuration are integral parts of the process.

This package complements the TYPO3 Integrator Plugin. Anyone developing extensions will generally find both very useful.

For upgrades and cleanup tasks

The TYPO3 Migrator Plugin is designed for projects where the technical infrastructure has evolved over the years and an update cannot simply be handled with a Composer update.

It supports migrations from TYPO3 v11 to v12, from v12 to v13, and from v13 to v14. It also helps with planning an upgrade strategy, merging multiple site packages, replacing Gridelements with the Container extension, and migrating old CSS themes to Tailwind CSS v4.

A clear separation is especially worthwhile for this type of work. A migration agent should first check for dependencies, outdated extensions, data structures, and risks. Afterward, they can create a transparent migration plan. This saves a great deal of time during analysis, preparation, documentation, and ultimately during the execution and testing of the migration.

Here, too, the TYPO3 Integrator Plugin remains a useful tool. After an upgrade, forms, templates, SEO, routes, menus, and tests must continue to function properly.

Complete Plugin or Individual Skills

You can install all three collections as a complete Agent plugin. This is a good option if you work with TYPO3 regularly and want full access to the respective capabilities. The plugins follow the Agent Plugins v1.0.0 standard and can be used in Codex, Cursor, GitHub Copilot, and Visual Studio Code, among others.

Alternatively, you can install individual skills. This is useful if you need a specific component or are using a tool that does not (yet) support the Agent Plugins v1.0.0 standard, such as Antigravity, OpenCode, Windsurf, Zed, Trae, or Qoder.

This breakdown makes it easier: The Integrator Plugin is recommended for all TYPO3 projects. The Extension Developer Plugin is added if you build your own extensions. Use the Migrator Plugin for version jumps, consolidations, and major overhauls.

If you’d also like to create your own skills, agents, workflows, hooks, slash commands, or even your own agent plugins (regardless of TYPO3 projects), you’ll find the AI Skills Plugin for that purpose.