What problem does it solve? When a consumer and supplier live on the same deployable side, teams often either over-engineer the boundary with HTTP projections and generated types, or skip the boundary entirely and couple directly to the supplier's domain types. This Skill defines the light variant of a boundary: a code interface plus a contract test, nothing else. ## Core Features & Use Cases - Code-interface Port: Keeps the Port as a plain code interface that the consumer depends on and the Adapter implements, with no HTTP/OpenAPI projection. - In-process contract testing: Instantiates the consumer-driven abstract test class twice — once on a fake for green-on-its-own (D1), once on the real Adapter for boundary welding (D2). - Published Language typing: Pins boundary types to primitives or shared-kernel types instead of the supplier's domain types, preventing coupling even within one process. - Use Case: When a building-block manifest marks boundary.projection = in-process, load this Skill alongside realize-port and realize-adapter to implement the seam without cross-deploy ceremony. ## Quick Start Ask the agent to implement the in-process boundary for a building block whose manifest sets boundary.projection to in-process, using a code interface and a consumer-driven contract test.
