mcpField
E
enterprise-integration-api-developer

enterprise-integration-api-developer

github.com/rade-nugrohoDevelopment1238 installsUpdated 23w ago
Repository

About enterprise-integration-api-developer

An API development skill for enterprise integration platforms and connected systems. It covers contracts, event-driven flows, model mapping, security, observability, and interface lifecycle management.

Key features

  1. 01Design REST or GraphQL API contracts
  2. 02Author OpenAPI and AsyncAPI specifications
  3. 03Build reliable event-driven flows
  4. 04Define canonical models and field mappings
  5. 05Configure gateways, auth, and access policies
  6. 06Plan observability and API lifecycle

Use cases

  1. 01Specify API boundaries between enterprise systems
  2. 02Design idempotency and failure handling for async flows
  3. 03Connect partner endpoints and define authentication
  4. 04Plan API deprecation and compatibility changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rade-nugroho/agentic-enteprises-skill --skill enterprise-integration-api-developer

After installing, type/enterprise-integration-api-developerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
api_design_and_contracts.md
canonical_models_and_transformations.md
enterprise_integration_api_scope.md
event_driven_and_reliability.md
operations_observability_and_lifecycle.md
security_governance_and_gateways.md

Details

From the project README

Enterprise Integration API Developer

When to Use

  • Design enterprise integration platforms—hub, mesh-adjacent services, or hybrid iPaaS patterns
  • Specify REST or GraphQL APIs with versioning, pagination, filtering, and error contracts
  • Author OpenAPI or AsyncAPI specifications and consumer-driven contract tests
  • Implement event-driven flows—topics/queues, outbox, idempotent consumers, compensating actions
  • Define canonical models, mappings, and anti-corruption layers between bounded contexts
  • Stand up API gateways, B2B partner endpoints, webhooks, and transformation/routing rules
  • Apply OAuth2/OIDC, API keys, mTLS, and scope models for internal vs external callers
  • Plan observability—correlation IDs, trace propagation, structured errors, DLQ operations
  • Manage lifecycle—deprecation headers, sunset policy, backward-compatible schema evolution

When NOT to Use

  • X12/EDIFACT segment mapping, 997/APERAK, AS2/VAN EDI transport → edi-engineer
  • Classified air-gapped build, ATO evidence, cleared pipeline promotion only → classified-software-devsecops-engineer
  • VRP, MIP, scheduling, or solver-based optimization → operations-research-algorithm-developer
  • Generic application CRUD, UI, or single-service features without integration architecture → senior-software-engineer
  • CI/CD pipeline YAML, GitOps, and deploy mechanics only → devops
  • Landing zone, VPC, and managed cloud resource design → cloud-engineer
  • Enterprise-wide cloud reference architecture and migration roadmap → cloud-architect
  • Internal developer platform golden paths and portals → platform-engineer

Related skills

NeedSkill
EDI standards, segments, partner certificationedi-engineer
Application services and code qualitysenior-software-engineer
CI/CD, GitOps, integration service deploydevops
Cloud messaging, networking, IAM for integrationscloud-engineer
Cloud reference architecture and landing zonescloud-architect
IDP, golden paths, paved-road templatesplatform-engineer
Classified DevSecOps and promotion boundariesclassified-software-devsecops-engineer
OR models, routing, allocation solversoperations-research-algorithm-developer
Enterprise architecture ADRs and cross-system reviewsenior-system-architecture
Pipeline security and supply chaindevsecops

Core Workflows

1. Scope and integration boundaries

Define systems of record, sync vs async boundaries, partner vs internal surfaces, and non-goals.

See references/enterprise_integration_api_scope.md.

2. API design and contracts

Model resources, errors, versioning, and publish OpenAPI/AsyncAPI with contract tests.

See references/api_design_and_contracts.md.

3. Event-driven reliability

Choose messaging patterns, idempotency keys, outbox, sagas/choreography, and failure handling.

See references/event_driven_and_reliability.md.

4. Canonical models and transformation

Define canonical schemas, ACLs, mapping rules, and validation at ingress/egress.

See references/canonical_models_and_transformations.md.

5. Security, gateways, and governance

Configure gateways, auth, rate limits, partner onboarding, and policy enforcement.

See references/security_governance_and_gateways.md.

6. Operations, observability, and lifecycle

Instrument traces and metrics, operate DLQs, and execute deprecation and compatibility plans.

See references/operations_observability_and_lifecycle.md.

Outputs

  • Integration context diagram — systems, channels, sync/async, trust zones
  • Contract artifacts — OpenAPI/AsyncAPI, JSON Schema, example payloads, error catalog
  • Mapping spec — canonical fields, transforms, validation rules, idempotency strategy
  • Runbook — replay, DLQ drain, partner cutover, rollback, compatibility matrix
  • ADR or decision log — orchestration vs choreography, versioning, auth model

Principles

  • Prefer contracts and schemas over tribal knowledge; test consumers in CI
  • Make idempotency and deduplication explicit at every external boundary
  • Separate partner (B2B) surfaces from internal mesh traffic—different auth, SLOs, and change windows
  • Design for observable failures—correlation ID end-to-end, structured errors, actionable DLQs
  • Ship backward-compatible changes; document sunsets and give consumers migration time

Comments

Markdown supported