Metadata Bundle Laravel Package

Use this skill whenever the user wants to create, scaffold, architect, or configure a Symfony bundle (reusable PHP package for Symfony 7+/8+). Triggers include: 'create a bundle', 'symfony bundle', 'AbstractBundle', 'bundle structure', 'bundle skeleton', 'reusable symfony component', 'bundle configuration', 'DI extension', 'service container for bundle', 'configure()', 'loadExtension()', 'prependExtension()', 'bundle best practices', 'composer.json for bundle', 'SOLID bundle'. Also trigger when the user is building any reusable Symfony package, even if they don't explicitly say 'bundle'. Do NOT trigger for application-level Symfony development that doesn't involve creating a distributable package.

Advanced Symfony bundle patterns: compiler passes, event system, security voters, conditional service registration, configuration validation, deep merge pitfalls, cache warmers, and semantic versioning contracts. Referenced from the main symfony-bundle-core skill for deeper topics.

Use this skill when creating or managing Doctrine ORM entities within a Symfony bundle. Triggers include: 'doctrine entities in bundle', 'bundle entity mapping', 'XML mapping doctrine', 'orm.xml bundle', 'doctrine bundle integration', 'entity in reusable bundle', 'bundle database model'. Also trigger when the user asks about mapping strategies for distributable Symfony packages, overriding entity metadata, or why PHP attributes shouldn't be used for bundle entities. Do NOT trigger for application-level Doctrine usage.

Use this skill when creating Symfony Flex recipes for bundle distribution, writing manifest.json files, configuring automatic bundle registration, importmap injection, environment variable scaffolding, or preparing a bundle for publication on Packagist with Flex integration. Trigger when: 'flex recipe', 'manifest.json symfony', 'bundle distribution', 'publish symfony bundle', 'packagist bundle', 'recipes-contrib', 'copy-from-recipe', 'auto-configure bundle install', 'plug and play bundle'. Also trigger when the user says 'I want users to install my bundle with zero config' or 'automate the bundle setup'. Do NOT trigger for general Composer package publishing unrelated to Symfony bundles.

Configure quality assurance tooling for Symfony bundles: Makefile, Deptrac architecture enforcement, GrumPHP pre-commit hooks, PHPStan level 9, PHP-CS-Fixer strict @Symfony, Infection mutation testing, composer audit security checks, GitHub Actions CI for Symfony 7+8. Trigger when: 'quality', 'CI', 'makefile', 'deptrac', 'phpstan', 'grumphp', 'infection', 'composer audit', 'security check', 'coding standards', 'architecture', 'publish bundle', 'open source bundle'.

Use this skill whenever building or integrating frontend assets in a Symfony bundle: AssetMapper, Stimulus controllers, Twig Components (UI-only and Live), importmaps, CSS/JS distribution, lazy-loading, package.json UX metadata. Trigger when: 'stimulus controller in bundle', 'assetmapper bundle', 'twig component bundle', 'bundle assets', 'UX bundle', 'live component bundle', 'bundle frontend', 'no-build bundle'. Do NOT trigger for application-level asset management.

Quality tooling configuration and CI pipeline for Symfony bundles

Testing patterns for Symfony bundle test suites

Stimulus controller and AssetMapper conventions for Symfony bundle assets

Strict PHP code style for Symfony bundle source code

Symfony bundle conventions, SOLID principles, Contract pattern, final readonly architecture

Twig component, Live Component, and template conventions for Symfony bundles

XML service and Doctrine mapping conventions for Symfony bundles