typo3-update

Write TYPO3 code compatible with v13 and v14 environments.

33|6|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typo3-update
Source: https://github.com/dirnbauer/webconsulting-skills/tree/main/skills/typo3-update
Command: npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to building TYPO3 extensions and code that remains compatible across TYPO3 v13 and v14, with a preference for v14, ensuring smoother migrations and long-term maintenance.

Core Features & Use Cases

  • Dual-version compatibility patterns and migration guidance for TYPO3 extensions.
  • Best practices for constraints, upgrades, and code structure across v13/v14.
  • Use case: Teams preparing a TYPO3 project for a v13/v14 upgrade can follow this guide to ensure a minimal-risk transition.

Quick Start

Open this skill and follow the migration checklist to prepare a TYPO3 v13/v14 upgrade plan.

Frequently Asked Questions about typo3-update

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

FAQPage Schema
How do I make a TYPO3 extension compatible with both v13 and v14?

To make a TYPO3 extension compatible with v13 and v14, apply dual-version constraints and compatible coding patterns that ensure your code structure runs smoothly across both environments while preferring v14 features.

What is the best way to plan a TYPO3 v13 to v14 upgrade?

The best way to plan a TYPO3 v13 to v14 upgrade is to follow a structured migration checklist that applies dual-version compatibility patterns and best practices for extension constraints, ensuring a minimal-risk transition.

Do I need to update ext_emconf.php constraints for a TYPO3 v14 migration?

Yes, updating ext_emconf.php constraints is necessary for a TYPO3 v14 migration to specify dual-version compatibility and ensure your extension properly declares its supported TYPO3 environment range.

Can I use Composer to manage TYPO3 dual-version dependencies for v13 and v14?

You can use Composer to manage TYPO3 dual-version dependencies by defining compatible version constraints that allow your extension installation across both v13 and v14 environments during the migration process.

Why does my TYPO3 extension break after upgrading to v14?

A TYPO3 extension breaks after upgrading to v14 when it lacks dual-version compatibility patterns, requiring you to apply updated migration strategies and coding constraints to ease cross-version maintenance.

Are there specific coding patterns for maintaining TYPO3 extensions across v13 and v14?

Specific compatible coding patterns for maintaining TYPO3 extensions across v13 and v14 involve applying dual-version constraints, following best practices for code structure, and using migration strategies that prefer v14 standards.