create-integration

Scaffold external integration layers for API clients, AWS, Kafka, or RabbitMQ.

2|Updated May 2, 2026

Search Tags:#aws #integration #dependency injection #kafka #resilience patterns #external api #rabbitmq

Ready to run

npx skills add https://github.com/andrecini/dotnet-squad-copilot-agent --skill create-integration-andrecini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-integration
Source: https://github.com/andrecini/dotnet-squad-copilot-agent/tree/main/.claude/skills/create-integration
Command: npx skills add https://github.com/andrecini/dotnet-squad-copilot-agent --skill create-integration-andrecini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual, error-prone work of building consistent integration layers for external services, messaging systems, and cloud providers while keeping your architecture rules intact.

Core Features & Use Cases

End-to-End Integration Scaffolding: Generates Domain contracts, Infrastructure implementations, validators, AutoMapper profiles, and integration tests according to the repository’s Clean Architecture rules.
Multi-Platform Support: Covers API clients, AWS services, Kafka producers/consumers, and RabbitMQ producers/consumers with the right resilient patterns (including retry/dead-letter naming guidance).
Safety and Consistency Guardrails: Enforces restricted scope to integration layers, requires configuration via appsettings for sensitive data, and asks before overwriting existing files.

Quick Start

Tell the AI which integration type, name, scope, and (for Kafka/RabbitMQ) whether you want a producer, consumer, or both, and it will generate the full integration scaffolding in the correct Domain and Infrastructure folders.

Frequently Asked Questions about create-integration

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

FAQPage Schema

How do I scaffold a Kafka integration layer in a Clean Architecture project?▼

Scaffolding a Kafka integration layer generates Domain contracts and Infrastructure implementations for producers and consumers under dedicated Integration folders. It applies resilient messaging conventions, including retry and dead-letter naming guidance, while enforcing strict architectural separation.

What is the best way to generate RabbitMQ producers and consumers with resilient patterns?▼

Generating RabbitMQ producers and consumers involves creating Domain contracts and Infrastructure implementations with applied resilient patterns. The process enforces strict architectural separation and requires sensitive configuration via appsettings without touching Presentation or Application endpoints.

How does dependency injection registration work for external API client integrations?▼

Dependency injection registration for external API clients is generated automatically within the Infrastructure layer. The scaffolding produces DI registrations alongside AutoMapper mappings, validators, and integration tests, ensuring the external dependency is wired correctly without manual configuration errors.

Can I add AWS service integrations without modifying my Application or Presentation endpoints?▼

Adding AWS service integrations is restricted to the Domain and Infrastructure layers. The scaffolding produces integration files exclusively under [component].Domain/Integrations and [component].Infrastructure/Integrations, ensuring your Application and Presentation endpoints remain untouched.

How do I handle sensitive configuration for external API integrations?▼

Handling sensitive configuration for external API integrations requires using appsettings. The scaffolding enforces this safety guardrail by routing sensitive data through appsettings configuration files, preventing hardcoded secrets in the generated Domain contracts or Infrastructure implementations.

What are the limitations of automated integration scaffolding for messaging systems?▼

A limitation of automated integration scaffolding is its strict scope restriction, meaning it only generates files under the Domain and Infrastructure Integration folders. It also prompts before overwriting existing files, requiring manual intervention for conflicts outside its architectural boundaries.