Claude Cursor Skill

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

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download goldziher-ai-rulez-internal_builtins_universal_polyglot-bindings_skills_bindings-ca967ad.zip · 0 KB

goldziher/ai-rulez 162 16 forks MIT Updated 5h ago

Part of goldziher/ai-rulez — 151 skills

Install

skills CLI

npx skills add https://github.com/Goldziher/ai-rulez/tree/main/internal/builtins/universal/polyglot-bindings/skills/bindings

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install goldziher-ai-rulez@llmmart

Git git clone https://github.com/Goldziher/ai-rulez.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole goldziher/ai-rulez collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Files (ai-rulez)

SKILL.md 1 KB

---
name: bindings
description: "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."
---

- 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.