srednoff888-art site api integration boundaries
Workflow
- Confirm the business outcome, owner, source data, constraints, and success metric.
- Inspect the project and available account or analytics evidence before proposing changes.
- Use official documentation for current platform behavior and retain source provenance.
- Produce an evidence-backed plan with assumptions, dependencies, and measurable validation.
- 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.