What problem does it solve? When two bounded contexts interact, coupling the consumer to the supplier's domain types recreates the very dependency the boundary was meant to remove. This Skill realizes a Port — the consumer-owned, read-only interface that declares what a consumer context needs from another — using only primitives or shared-kernel types, so the inter-context boundary stays clean and independently testable. ## Core Features & Use Cases - Consumer-owned port realization: Generates the interface expressing the consumer's need, exposing named predicates (e.g. sellable) rather than raw supplier fields, with identity types pinned from the manifest. - Reusable contract test: Produces an abstract test class plus a factory and a fake implementation, so the consumer is green on its own and the same test later welds the real Adapter (D2). - tests_nl translation: Converts the user's natural-language boundary tests into concrete contract test cases. - Use Case: While building a Sales context that needs product data from Catalog, the worker loads this Skill to declare a Sales-owned port typed with Int identities, plus a contract test with a fake — later projected into OpenAPI or an event-schema CDC by the seam-cross-deploy skill if the boundary crosses deploys. ## Quick Start Ask the worker to realize the port block defined in your building-block manifest, including its consumer-driven contract test with a fake supplier.
