What problem does it solve? Adding a new API integration to a codebase that already has connectors often produces a foreign architecture: vendor SDK conventions, mismatched error handling, and missing registration or tests. This Skill ensures a new connector mirrors the repo's established patterns so it stays maintainable. ## Core Features & Use Cases - Pattern Discovery: Inspects at least two existing connectors to map file layout, config, auth, transport, error taxonomy, registration, and test fixtures before writing code. - Surface Narrowing: Defines only the auth flows, entities, operations, pagination, and rate limits the repo actually needs instead of the vendor's full API surface. - Layered Construction: Builds config, client/transport, mapping, entrypoint, registration, and tests in the repo's own layers, with a checklist covering secrets, error types, retries, and discovery wiring. - Use Case: When asked to "add a Slack provider" or "build a Jira connector", the Skill guides the AI to copy the newest existing integration's shape, map vendor fields to domain types, and ship tests mirroring existing fixtures. ## Quick Start Ask the AI to add a new integration for a third-party API to this repository following the existing connector patterns.
