What problem does it solve? Adding a new API integration often leads to inconsistent architecture when developers copy vendor docs or invent new patterns instead of following the host repository's established connector style, resulting in fragmented codebases that are hard to maintain. ## Core Features & Use Cases - Pattern Matching: Inspects at least two existing in-repo connectors to map file layout, config schema, auth model, error handling, and test style before writing any code. - Repo-Native Layering: Guides building the integration in the repository's own slices: config/schema, client/transport, mapping layer, provider entrypoint, registration, and tests. - Guardrails Against Drift: Prevents inventing a second integration architecture, cargo-culting outdated connectors, or stopping at transport code without registry wiring and docs. - Use Case: When asked to "add a Slack provider following the existing pattern," the Skill first studies current providers, then produces a connector that looks native to the codebase, complete with config validation, retry/pagination conventions, and matching tests. ## Quick Start Ask the AI to build a new Jira connector for this project following the existing integration pattern.
