TYPO3 Conformance
Evaluate TYPO3 extensions for conformance to official coding standards, architecture patterns, and best practices. Automated validation scripts for file structure, PSR-12 compliance, dependency injection, testing infrastructure, and priority-based conformance scoring.
Install
Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.
-
Claude Code via this marketplace /plugin install typo3-conformance@netresearch-claude-code-marketplaceFirst add the marketplace once in Claude Code:
/plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, seeClaude Code plugin setupA plugin can include several skills and additional components. -
npx interactive skill selection npx skills add https://github.com/netresearch/typo3-conformance-skillRequires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Uses the skills CLI from
skills.shInstalls skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route. -
composer require PHP project, as a package composer require netresearch/typo3-conformance-skillAllow the Composer skill installer to activate and approve skill registration when prompted. Requires
netresearch/composer-agent-skill-pluginDiscovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup. -
composer skills:add PHP project, direct source composer skills:add netresearch/typo3-conformance-skillInstall and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by
netresearch/composer-agent-skill-pluginPins source repositories without a Packagist package and records them incomposer.skills.lock. Runtime dependencies remain separate.
What you can do with it
- ✅ check-conformance.sh - Main orchestration script
- 📁 check-file-structure.sh - File structure and directory validation
- 📝 check-coding-standards.sh - PSR-12 and TYPO3 code style checks
- 🏗️ check-architecture.sh - Dependency injection and architecture patterns
- 🧪 check-testing.sh - Testing infrastructure and coverage analysis
- 📊 generate-report.sh - Comprehensive conformance report generation
- version-requirements.md - Official TYPO3 and PHP version compatibility matrix
- extension-architecture.md - TYPO3 file structure standards
- coding-guidelines.md - PSR-12 and TYPO3 code style guide
- php-architecture.md - Dependency injection and architectural patterns
- testing-standards.md - Unit, functional, and Playwright E2E testing
- best-practices.md - Real-world patterns and project infrastructure
- runtests-validation.md - Validate Build/Scripts/runTests.sh against Tea extension reference
- development-environment.md - Validate DDEV/Docker development environment setup
- directory-structure.md - Validate .Build/ vs Build/ directory separation and organization
- excellence-indicators.md - Optional quality features for exceptional extensions (0-22 bonus points); Community & Internationalization: Crowdin, issue templates, .gitattributes, README badges; Advanced Quality Tooling: Fractor, TYPO3 CodingStandards, StyleCI, Makefile, CI matrix; Documentation Excellence: feature coverage for the extension scope (not file counts), modern tooling (guides.xml, screenshots.json); Extension Configuration: ext_conf_template.txt, composer doc scripts, multiple Sets
- georgringer/news - Community reference extension demonstrating excellence patterns
- Build/phpstan/phpstan.neon - PHPStan Level 10 with advanced security and type safety
- Build/rector/rector.php - Automated TYPO3 migrations and refactoring
- Build/php-cs-fixer/php-cs-fixer.php - TYPO3 coding standards with parallel execution
- Build/composer-unused/composer-unused.php - Dependency health monitoring
- Build/typoscript-lint/TypoScriptLint.yml - TypoScript quality enforcement
- Build/eslint/.eslintrc.json - JavaScript/TypeScript linting
- Build/stylelint/.stylelintrc.json - CSS/SCSS quality checks
- Build/playwright/ - Playwright E2E and accessibility testing (Node >=22.18)
- .github/workflows/publish-to-ter.yml - TER publishing workflow
What you get back
- An extension conformance report with a summary table and an action checklist for the checks performed.
What it expects in your project
Check the source README for current examples, requirements and limitations. Open full README