add-bc-contract

Inter-service communication contracts define how one bounded context (BC) reads data from another. This Skill generates a Contract interface with provide() and provideAll() methods, plus a read-only Provider implementation using Finder, automatically wired via services.yaml for dependency injection across service boundaries.

Use the provider pattern when a BC needs read-only access to another BC's data without direct repository coupling. Providers enforce architectural boundaries, expose domain data safely via explicit contracts, and maintain Deptrac dependency rules—repositories couple contexts too tightly and violate bounded-context isolation.

Implement a Contract interface in the data-providing BC that returns EntityData through provide(uuid) and provideAll(ids) methods. The Skill auto-generates the Provider, configures it in services.yaml, and validates the implementation against architecture rules (cs-fixer, stan, deptrac).

Yes. Providers expose domain data as read-only iterables, making them ideal for populating Twig component select options across BCs. The Contract interface standardizes the shape; Finder queries return only necessary fields without repository-level coupling.

The Skill runs cs-fixer for code style, PHPStan for static analysis, deptrac analyse to verify boundary rules are maintained, and qa checks. This ensures the generated Contract and Provider comply with architecture constraints and code standards.

Yes. Provider contracts align with DDD by formalizing BC boundaries, treating data exposure as explicit contracts rather than implicit dependencies, and preventing anemic data access patterns through Finder-based, read-only providers.