skills.rest
Entelligentsia
EntelligentsiaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

anti-corruption

Translate external system models into domain-safe representations with an Anti-Corruption Layer.

1|1|Updated Mar 30, 2026
Search Tags:#domain-driven-design#gateway#acl#legacy-migration#integration-patterns#strangler-pattern#anti-corruption
One-click install
npx skills add https://github.com/Entelligentsia/skillforge --skill anti-corruption
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: anti-corruption
Source: https://github.com/Entelligentsia/skillforge/tree/main/design-patterns/skills/anti-corruption
Command: npx skills add https://github.com/Entelligentsia/skillforge --skill anti-corruption

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External systems often carry vocabulary, formats, and constraints that pollute your domain model. Anti-Corruption patterns create a clear boundary and a translation layer to keep the core domain clean.

Core Features & Use Cases

  • Anti-Corruption Layer (ACL): a dedicated boundary that translates between domain concepts and external models.
  • Gateway and Facade: decouple domain services from external interfaces and simplify multi-step integrations.
  • Strangler Fig: incremental migration strategy that replaces legacy components with new implementations without downtime.

Quick Start

Implement an explicit ACL between your domain and the external API and plan a Strangler Fig migration to gradually replace legacy components.

Frequently Asked Questions about anti-corruption

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I protect my domain model from legacy system pollution during integration?▼

To protect domain model integrity from legacy system pollution, implement an Anti-Corruption Layer (ACL) that acts as a dedicated boundary to translate external concepts into domain-safe representations. This keeps your core domain clean.

What is an anti-corruption layer and when do I need it for third-party integrations?▼

An anti-corruption layer is a translation boundary needed for third-party integrations when external systems carry vocabulary and formats that risk polluting your domain. It translates external models into domain-safe representations.

How do I gradually migrate legacy components without downtime?▼

Gradually migrate legacy components without downtime by applying the Strangler Fig pattern, an incremental migration strategy that systematically replaces legacy components with new implementations over time.

Does domain-driven design require a gateway interface for external API integrations?▼

Domain-driven design uses gateway interfaces for external API integrations to decouple domain services from external interfaces. This facade simplifies multi-step integrations and prevents external models from polluting domain behavior.

What is the best way to decouple domain services from external system interfaces?▼

The best way to decouple domain services from external system interfaces is implementing a gateway facade. This pattern abstracts multi-step integrations and works with an ACL to translate external models into domain-safe representations.

When should I not use an anti-corruption layer for software integration?▼

You should not use an anti-corruption layer when the external system's vocabulary perfectly aligns with your domain model or when integration overhead outweighs the benefit of maintaining domain purity for simple, temporary data mappings.

Related Skills

Explore More Software Engineering Skills→
mariotoffiamariotoffia

implement-acl

Implement Anti-Corruption Layers to isolate domain models from external systems.

Community
Advanced
lamb92009lamb92009

legacy-modernizer

Plan and execute strangler fig migrations for legacy systems.

Community
Advanced
sachio222sachio222

domain-driven-design

Model core business domains with bounded contexts, aggregates, and ubiquitous language.

Community
Advanced
slbugslbug
7

ruby-contexts

Design Ruby application boundaries for service layers, command objects, and adapters.

Community
Intermediate