metodologia-integration-architecture

Map integration landscapes and define API contracts for multiple systems.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-integration-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metodologia-integration-architecture
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/architecture/integration-architecture
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-integration-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System connectivity across enterprise environments is complex and error-prone. This skill produces architecture artifacts that help teams map integrations, govern API contracts, and design reliable data flows.

Core Features & Use Cases

  • Map integration landscapes, identify data flows, and establish governance for API contracts and versioning.
  • Define and document API contracts (OpenAPI, AsyncAPI) and data mappings to ensure consistent integration patterns across point-to-point, ESB, iPaaS, and event-driven architectures.
  • Produce sequence diagrams for critical flows and provide guidance for error handling, latency, and security considerations.
  • Use Case: For a multi-system enterprise, generate an end-to-end architecture artifact set to align developers, operators, and governance bodies.

Quick Start

Provide a system context and ask the skill to generate the landscape and contracts.

Frequently Asked Questions about metodologia-integration-architecture

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

FAQPage Schema
How do I design API contracts for multiple enterprise systems?

Yes, you can map integration patterns like point-to-point, ESB, iPaaS, and event mesh architectures. The skill evaluates your system context to produce landscape maps and recommend the appropriate integration pattern for reliable enterprise connectivity.

What is the best way to document data flows and error handling for integration architectures?

The best way to document data flows and error handling is by generating sequence diagrams for critical processes. The architecture artifacts include explicit considerations for latency, security, and error handling to align developers and governance bodies.

Can I use this to govern API versioning across diverse tech stacks?

Yes, you can use this to govern API versioning across diverse tech stacks. It establishes governance for API contracts and versioning, ensuring consistent integration patterns and reliable data flows throughout the enterprise environment.

Does this skill work without any external dependencies or components?

Yes, this skill works without external dependencies or components. You simply provide your system context, and it generates the end-to-end architecture artifact set, including landscape maps, API contracts, and sequence diagrams, without requiring prior setup.