# Bindings

> Cross-language binding architecture rules: bindings as minimal glue, canonical API surface ordering (core, ABI, language), per-language test suites in CI, generated-code discipline, and error/async boundary preservation. Load when designing or reviewing polyglot language bindings for a shared core.

- Skill: `goldziher/bindings` (Agent Skill)
- Install (CLI): `npx skillmds@latest add goldziher/bindings`
- Raw SKILL.md: https://api.skillmd.com/api/skills/goldziher/bindings/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: goldziher (https://skillmd.com/u/goldziher)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/goldziher/bindings

---


- Bindings are minimal glue: call the core library, convert types, convert errors — no business logic.
- Canonical surface: core API first, stable native ABI second, language bindings third.
- Keep integrations and framework adapters outside language bindings unless they are the binding's public purpose.
- Give each binding its own language-native test suite and run it in CI.
- Generated binding and e2e code must not be hand-edited. Change the source schema, generator, or core API instead.
- Error conversion must preserve context across every boundary: message, numeric code when available, and operation.
- Async boundaries must match host runtime conventions; do not block event loops, schedulers, or UI threads.