api-connector-builder

Topics in the source

• API Connector Builder
• When to Use
• Guardrails
• Workflow
• 1. Learn the house style
• 2. Narrow the target integration
• 3. Build in repo-native layers
• 4. Validate against the source pattern

Use this when the job is to add a repo-native integration surface, not just a generic HTTP client. The point is to match the host repository's pattern: connector layout config schema auth model error handling test style registration/discovery wiring "Build a Jira connector for this project" "Add a Slack provider following the existing pattern" "Create a new integration for this API" "Build a plugin that matches the repo's connector style" do not invent a new integration architecture when the repo already has one do not start from vendor docs alone; start from existing in-repo connectors first do not stop at transport code if the repo expects registry wiring, tests, and docs do not cargo-cult old connectors if the repo has a newer current pattern Inspect at least 2 existing connectors/providers and map: file layout abstraction boundaries config model retry / pagination conventions registry hooks test fixtures and naming Define only the surface the repo actually needs: auth flow key entities core read/write operations pagination and rate limits webhook or polling model Typical slices: config/schema client/transport mapping layer connector/provider entrypoint registration tests The ne

This is an excerpt. Refer to the complete source and its current requirements.