What problem does it solve? Managing database schema changes in PHP backends is error-prone when entities, XML mappings, repositories, and migrations drift out of sync, especially across both relational (Doctrine ORM) and MongoDB (Doctrine ODM) persistence stacks. ## Core Features & Use Cases - Dual-mapper schema management: Generates versioned migrations with doctrine:migrations:* for doctrine-orm, or syncs collections and indexes with doctrine:mongodb:schema:* for doctrine-odm. - Hexagonal architecture enforcement: Places entities in the Domain layer, repository implementations in Infrastructure, and XML mappings in config/doctrine/, keeping Domain classes framework-agnostic. - Custom identifier types and indexing: Uses ulid and domain_uuid identifier types, defines indexes in XML mappings, and covers MongoDB compound, sparse, TTL, and text indexes. - Use Case: When adding a new Customer entity with an email field, the skill guides creating the Domain class, the .orm.xml or .mongodb.xml mapping, the repository pair, and then applying and validating the schema change with the correct console commands. ## Quick Start Ask the assistant to create a new Customer entity with name and email fields, generate its Doctrine XML mapping and repository, and apply the resulting migration or schema update.
