How do I install the Binding Architecture skill?

Run npx skillmds@latest add kreuzberg-dev/binding-architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Binding Architecture safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Binding Architecture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Binding Architecture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Binding Architecture?

kreuzberg-dev (@kreuzberg-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Binding Architecture by kreuzberg-dev

Name: Binding Architecture
Author: kreuzberg-dev

Binding Architecture

Architecture rules for the polyglot binding layer and the C FFI boundary — crate naming, distribution paths, ownership and null-safety invariants, error-context propagation, and async patterns. Load when designing or editing language bindings, the C ABI, cbindgen headers, or FFI type/error conversions.

File contents

Binding Architecture

Bindings

Bindings are minimal glue: call Rust core, convert types, convert errors — no business logic
Canonical surface: Rust core API first, C FFI ABI second, language bindings third; integrations/adapters sit outside bindings
Crate naming: {lib}-py (PyO3), {lib}-node (NAPI-RS), {lib}-rb (Magnus), {lib}-php (ext-php-rs), {lib}-wasm (wasm-bindgen), {lib}-ffi (C FFI), {lib}-jni (JNI)
Distribution paths: packages/python/ (PyPI), typescript/ (npm), ruby/ (RubyGems), php/ (Composer), go/ (Go module), java/ (Maven), csharp/ (NuGet), dart/ (pub.dev), swift/ (SwiftPM), kotlin-android/ (Maven/Gradle), r/ (CRAN/GitHub), zig/ (Zig package)
Each binding has its own language-native test suite — 80%+ coverage
Generated e2e code lives under e2e/{language}/ and is not hand-edited
Error conversion must preserve context (message + numeric code) at every FFI boundary
Async: pyo3_asyncio (Python), native #[napi] async (TS), Fiber (Ruby), block on Tokio via FFI only at sync host boundaries

FFI and language interop

Every pointer has one owner, documented with SAFETY comments
Opaque handles only — never expose Rust types directly, use #[repr(transparent)] wrappers
Null safety: check ALL pointers before use, return null + error code on failure
Allocate/free pairs: every _new() has a matching _free(), caller owns *mut
Every unsafe block has a SAFETY comment: what invariant, why it holds, what breaks if violated
Generate C headers with cbindgen — CI verifies generated headers match committed
C ABI is the stable native contract for Go, Java/JNI, C#, Dart, Swift, Kotlin Android, Zig, and R wrappers
Semantic versioning for C headers, struct layouts frozen at MAJOR.MINOR boundaries
All exported functions use #[no_mangle] extern "C"
Rust Result<T, E> → host exceptions via dedicated conversion functions at every boundary
Preserve error context across boundaries: message, numeric code (1000+), source location, cause chain

---name: binding-architecturedescription: Architecture rules for the polyglot binding layer and the C FFI boundary — crate naming, distribution paths, ownership and null-safety invariants, error-context propagation, and async patterns. Load when designing or editing language bindings, the C ABI, cbindgen headers, or FFI type/error conversions.---# Binding Architecture## Bindings- Bindings are minimal glue: call Rust core, convert types, convert errors — no business logic- Canonical surface: Rust core API first, C FFI ABI second, language bindings third; integrations/adapters sit outside bindings- Crate naming: {lib}-py (PyO3), {lib}-node (NAPI-RS), {lib}-rb (Magnus), {lib}-php (ext-php-rs), {lib}-wasm (wasm-bindgen), {lib}-ffi (C FFI), {lib}-jni (JNI)- Distribution paths: packages/python/ (PyPI), typescript/ (npm), ruby/ (RubyGems), php/ (Composer), go/ (Go module), java/ (Maven), csharp/ (NuGet), dart/ (pub.dev), swift/ (SwiftPM), kotlin-android/ (Maven/Gradle), r/ (CRAN/GitHub), zig/ (Zig package)- Each binding has its own language-native test suite — 80%+ coverage- Generated e2e code lives under e2e/{language}/ and is not hand-edited- Error conversion must preserve context (message + numeric code) at every FFI boundary- Async: pyo3_asyncio (Python), native #[napi] async (TS), Fiber (Ruby), block on Tokio via FFI only at sync host boundaries## FFI and language interop- Every pointer has one owner, documented with SAFETY comments- Opaque handles only — never expose Rust types directly, use #[repr(transparent)] wrappers- Null safety: check ALL pointers before use, return null + error code on failure- Allocate/free pairs: every \_new() has a matching \_free(), caller owns \*mut- Every unsafe block has a SAFETY comment: what invariant, why it holds, what breaks if violated- Generate C headers with cbindgen — CI verifies generated headers match committed- C ABI is the stable native contract for Go, Java/JNI, C#, Dart, Swift, Kotlin Android, Zig, and R wrappers- Semantic versioning for C headers, struct layouts frozen at MAJOR.MINOR boundaries- All exported functions use #[no_mangle] extern "C"- Rust Result\<T, E> → host exceptions via dedicated conversion functions at every boundary- Preserve error context across boundaries: message, numeric code (1000+), source location, cause chain

Frequently asked questions

Binding Architecture

File contents

Binding Architecture

Bindings

FFI and language interop

Related skills

Frequently asked questions

How do I install the Binding Architecture skill?

What does the Binding Architecture skill do?

Is Binding Architecture safe to use?

Which AI agents work with Binding Architecture?

Is Binding Architecture free to use?

Who published Binding Architecture?