Translate domain requests and responses to external system wire formats.
npx skills add https://github.com/reliant-labs/forge --skill adapter
Please help me install this Agent Skill. Skill: adapter Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/adapter Command: npx skills add https://github.com/reliant-labs/forge --skill adapter
Adapter skills eliminate tightly-coupled vendor code in your domain by isolating outbound integrations behind a narrow, vendor-neutral interface.
Scaffold a new outbound integration package named stripe-adapter by running a forge command that generates the canonical Service/Deps/New(Deps) shape and contract marker for you.
High-intent search queries and answers about installing and using this skill.
To isolate third-party API vendor code, use an adapter pattern that translates domain requests to external wire formats while keeping business logic vendor-neutral. This confines vendor-specific code to a leaf-node package behind a narrow service interface.
Mapping external HTTP API errors to domain errors requires an outbound integration layer that translates downstream vendor failures into domain-specific errors. This ensures callers handle failures consistently without knowing the underlying vendor response structure.
The best way to structure an outbound integration for a message broker is using an adapter package with a narrow service interface, context-first method signatures, and vendor-to-domain mapping to keep translation logic isolated from business workflows.
You need an adapter package to handle OAuth provider integrations when implementing them as leaf-node services. The adapter manages authentication, timeouts, and wire format translation, allowing your domain-oriented caller to depend on a vendor-neutral interface.
Implementing timeouts and retry policies for external storage backends is handled within the adapter layer. The adapter package structure requires context-first method signatures to manage these outbound integration concerns safely without affecting domain logic.
You should not use an adapter pattern alone when your outbound integration requires multi-step workflows or complex business decisions. Adapters should remain focused on translation logic, while interactors or services handle the broader workflow orchestration.
Vel-LabsCreate and validate ClearIntent adapters with typed success, degraded, and failure states.
bflandevTransform reviewed use cases into four-level RED TDD test suite skeletons.
sorodriguezzExchange real-time MQTT data in InterSystems IRIS productions.
bRRRITSCOLDImplement ports-and-adapters architecture for backend services in Go, Node/TypeScript, or Rust.
