# Site API Integration Boundaries

> Use for Site Building work when Codex should design resilient site API integration boundaries, failure states, caching, secrets, and contract tests.

- Skill: `srednoff888-art/site-api-integration-boundaries` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add srednoff888-art/site-api-integration-boundaries`
- Raw SKILL.md: https://api.skillmd.com/api/skills/srednoff888-art/site-api-integration-boundaries/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: srednoff888-art (https://skillmd.com/u/srednoff888-art)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/srednoff888-art/site-api-integration-boundaries

---


# site api integration boundaries

## Workflow

1. Confirm the business outcome, owner, source data, constraints, and success metric.
2. Inspect the project and available account or analytics evidence before proposing changes.
3. Use official documentation for current platform behavior and retain source provenance.
4. Produce an evidence-backed plan with assumptions, dependencies, and measurable validation.
5. Run only read-only diagnostics by default; gate external, paid, production, or publishing actions behind explicit approval.

## Domain Focus

design resilient site API integration boundaries, failure states, caching, secrets, and contract tests.

## Official Sources

https://web.dev/learn/ | https://www.w3.org/WAI/standards-guidelines/wcag/

## Guardrails

- Preserve existing design and content conventions unless the task calls for a redesign.
- Review external code, assets, and components for provenance, license, accessibility, performance, and dependency cost.
- Require explicit approval for production deployment, DNS, publishing, or irreversible migrations.