What problem does it solve? Integrating external services often leaks transport details (WebClient, Mono, remote DTOs) into business code, making callers hard to read, test, and evolve. This Skill wraps every downstream dependency in a self-contained client sub-package so callers see one domain-friendly service facade. ## Core Features & Use Cases - Pattern Selection Guidance: A human-in-the-loop decision tree chooses between a simple RestClient wrapper (1-4 endpoints), a lite client (5-9 endpoints), or the full five-layer SDK pattern (10+ endpoints or complex query DSLs). - Canonical Five-Layer Structure: Generates Service facade, CoreService orchestrator, thin Client transport, RequestBuilder/FilterMapBuilder, ResponseParser/ResponseVerifier, Config, and Constants classes. - Resilience & Error Translation: Applies Resilience4j circuit breakers and retries, and translates non-2xx responses into domain exceptions before they escape the client package. - Use Case: When adding a new Elasticsearch or Kafka dependency to a Spring Boot service, use this Skill to scaffold the complete client/<dep>/ package with tests, properties, and health-check wiring. ## Quick Start Apply the external-client skill to generate a client integration package for the new downstream service I need to call.
