When you need to add a new API integration to a repo that already has several, this keeps you from reinventing the wheel. It walks through learning the existing connector pattern first (file layout, config schema, auth model, test style), then building the new integration to match that house style instead of importing some generic HTTP client approach. The workflow is practical: inspect two existing connectors, map their structure, then build your Jira or Slack integration using the same layers and conventions. The guardrails are the real value here, specifically calling out not to cargo cult old patterns if the repo has evolved, and not to stop at transport code when the repo expects registry wiring and tests too.
npx -y skills add affaan-m/ecc --skill api-connector-builder --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
prisma/skills
firebase/agent-skills
Dexploarer/hyper-forge
itsmostafa/aws-agent-skills