Integration Patterns

Integrate data across systems using ETL, CDC, event streaming, and API patterns. Design robust, maintainable data integrations. Use when connecting disparate data sources or microservices.

48 stars 10 forksData & Analytics Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill integration-patterns
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/data-architecture/skills/integration-patterns ~/.claude/skills/integration-patterns

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Integration Patterns

Design robust data integrations between systems using time-tested patterns and technologies.

## Context

You are integrating data from multiple systems. Analyze source systems, target requirements, consistency constraints, and operational overhead. Read existing integration code or architecture documents.

## Domain Context

Based on Gregor Hohpe's _Enterprise Integration Patterns_ and modern streaming:

- **ETL (Extract-Transform-Load)**: Scheduled batch jobs; simple but high latency
- **ELT (Extract-Load-Transform)**: Load raw data first, transform in warehouse; flexible but storage intensive
- **CDC (Change Data Capture)**: Capture database changes in realtime; high fidelity but complex
- **Event Streaming**: Publish domain events to message brokers; loosely coupled but at-least-once semantics
- **API-Based Integration**: Synchronous queries; simple but tightly coupled and slower

## Instructions

1. **Choose Primary Pattern**: Batch ETL (cost-effective, simple)? CDC (realtime, high fidelity)? Event streams (loosely coupled, asynchronous)? Synchronous APIs (simple, tight coupling)? Often hybrid approach.

2. **Design Idempotency**: Ensure processing same data twice yields same result. Use unique identifiers, deduplication logic, or transactional sinks.

3. **Handle Schema Evolution**: Source schema changes. Build transformation layer that's resilient to new fields, deprecated fields, type changes.
Read the full skill on GitHub

Details

Skill name
integration-patterns
Path
architect/data-architecture/skills/integration-patterns/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Integration Patterns skill do?

Integrate data across systems using ETL, CDC, event streaming, and API patterns. Design robust, maintainable data integrations. Use when connecting disparate data sources or microservices.

How do I install the Integration Patterns skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Integration Patterns popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.