Third Party Api Intake
<!-- vcp-version: v0.9.5 -->
<!-- methodology-version: v1.4 -->
<!-- vcp-version: v0.8.4 -->
<!-- vcp-version: v0.8.2 -->
<!-- vcp-artifact: THIRD_PARTY_API_INTAKE_PROMPT -->
<!-- vcp-version: v0.8.2 -->
Read `protocols/integrations/third-party-api-intake.md` first.
Do not write integration code yet.
Classify the external API dependency, record auth/data/terms/fallback risks, update or plan `THIRD_PARTY_REGISTRY`, and report whether implementation should proceed, narrow, escalate or stop.when to use it
Community prompt sourced from the open-source GitHub repo Gudvin82/vibe-coding-protocols (NOASSERTION). A "Third Party Api Intake" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
Gudvin82/vibe-coding-protocols · NOASSERTION
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions