菜单
Use when merging two TYPO3 site packages, side-packages, or theme extensions into one TYPO3-compliant site package, consolidating files, TypoScript, site sets, Fluid templates, TCA overrides, Composer metadata, assets, or version compatibility.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Battle-tested TYPO3 Fluid template patterns for site package development. Use this skill when building or maintaining a TYPO3 v12+ site package — regardless of CSS framework. Covers the full template hierarchy (Layouts → Pages → Partials → Atoms), CMS-first content architecture with lib.dynamicContent, colPos propagation for sidebar-aware styling, responsive image handling, WCAG 2.1 AA accessibility patterns, and progressive-enhancement JavaScript. Complements the typo3-playwright-ddev and typo3-tailwind-migration skills.
Use when securing TYPO3 frontend forms (typo3/cms-form), frontend user registration forms (evoweb/sf-register), or installing/configuring Google reCAPTCHA (evoweb/recaptcha) in TYPO3 projects.
Migrate a TYPO3 theme from legacy/custom CSS to Tailwind CSS v4 in a DDEV environment. Use this skill when a TYPO3 project needs to convert its existing CSS-based site package to Tailwind utility classes while maintaining 1:1 visual parity. Covers the complete workflow from visual regression baseline capture through build pipeline setup, design token mapping, Fluid template migration, content element conversion, accessibility auditing, and cross-browser verification. Critical emphasis on regression-test-first approach — always capture baselines before any migration work begins.
Use when upgrading TYPO3 11 to TYPO3 12, checking extension compatibility, Composer blockers, Rector/Fractor migrations, deprecations, platform requirements, or planning a major-version migration. Covers analysis, planning, and execution of TYPO3 11 to 12 upgrades in Composer-based projects.
Use when upgrading TYPO3 12 to TYPO3 13, checking extension compatibility, Composer blockers, Rector/Fractor migrations, deprecations, platform requirements, or planning a major-version migration. Covers analysis, planning, and execution of TYPO3 12 to 13 upgrades in Composer-based projects.
Use when upgrading TYPO3 13 to TYPO3 14, checking extension compatibility, Composer blockers, Rector/Fractor migrations, deprecations, or planning a major-version migration. Covers analysis, planning, and execution of TYPO3 13 to 14 upgrades in Composer-based projects.
| name | typo3-merge-sitepackages |
| description | Use when merging two TYPO3 site packages, side-packages, or theme extensions into one TYPO3-compliant site package, consolidating files, TypoScript, site sets, Fluid templates, TCA overrides, Composer metadata, assets, or version compatibility. |
Merge two TYPO3 site packages into one target extension while preserving intentional customizations, applying an explicit conflict winner, and keeping the result compatible with the target TYPO3 version.
Which site package has priority and should overwrite conflicting settings and files from the other package?
composer.json or asking the user.typo3-site-config-sets: use when configuring site sets in TYPO3 v13+typo3-fluid-patterns: use when resolving differences or overriding Fluid layouts, partials, or templatesUse the following detailed resources located in this skill: