api-integratelisted

## STOP - Read before ANY tool call 1. Read `{{GUARDRAILS_PATH}}` 2. Read `{{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/SESSION.md`; load session-state for `$Cwd` 3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell 4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only 5. This skill body is **English**; user-facing prompts may be **(pt-BR)** ### Step -1 - Gate check (report in chat before continuing) ``` Gate check: [ ] guardrails.mdc read [ ] SESSION.md read; session-state loaded [ ] PIPELINE.md read (SDD skills only) [ ] User confirmed current action (sim) -> If any unchecked: STOP ``` --- # Skill: api-integrate ## Trigger Invoke when the user requests: `/api-integrate`, `integrate api`, `/api-integrate`, or asks to integrate endpoints from a schema. **Arguments (optional):** | Input | Meaning | |-------|---------| | Schema source | Path to local `openapi.json` / `swagger.yaml` or a remote metadata URL | | Target service name | Specific name for the generated client class / wrapper | ## Outcome A typed, modular, and robust API client containing: 1. Strongly typed DTO models (Request and Response contracts). 2. Clean service wrapper or client declarations using preferred libraries (e.g., Refit/HttpClient for C#, Axios/Fetch for TS/JS, HTTPX for Python). 3. Configured authentication headers, timeout limits, and robust network error wrappers. ## Lazy-load | When | Path (after `scripts/sync-cu