TYPO3 CKEditor 5 Development
Provides expert patterns and implementation guidance for developing custom CKEditor 5 plugins and configurations within TYPO3 v12+ environments.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Implementing command patterns and custom UI components like dropdowns
- Configuring TYPO3 RTE presets using YAML and PageTSConfig
- Registering ES6 modules and stylesheets for the TYPO3 backend
- Architecting custom CKEditor 5 plugins with schema and conversion definitions
- Executing structured migrations from CKEditor 4 to CKEditor 5
Use cases
- Building custom editor functionality for specific content element needs
- Upgrading TYPO3 extensions to support v12+ CKEditor 5 requirements
- Integrating CKEditor 5 into custom TYPO3 backend modules
FAQ
When should I use this Claude Code skill?
Invoke this skill when you need to build custom RTE features, define complex schema and converters, register backend ES6 modules, or upgrade legacy TYPO3 extensions that still rely on CKEditor 4.
What specific CKEditor 5 capabilities does it cover?
It covers the complete development lifecycle, including model-view conversion, schema definitions, command pattern implementation, and the creation of custom UI elements like dropdowns and toolbars.
What does the TYPO3 CKEditor 5 Development skill do?
This skill equips Claude with specialized knowledge to architect custom CKEditor 5 plugins, configure RTE presets via YAML, and handle the technical nuances of integrating rich text editing within the TYPO3 v12+ backend.
Can this skill assist with CKEditor 4 to 5 migrations?
Yes. It provides structured migration checklists and transformation patterns to help you convert legacy PageTSConfig and Javascript plugins into modern YAML configurations and ES6-based CKEditor 5 plugins.
How does this skill improve my TYPO3 development workflow?
It eliminates the guesswork in CKEditor 5's class-based architecture by providing instant, verified patterns for commands, UI components, and TYPO3-specific registration, significantly reducing debugging time.