agentleFS
VyrnexisVyrnexis/nim-agent-template/skills/nim-c-wrappers/SKILL.md

nim-c-wrappers

Skill4 starsChanged 3 months agoMITView on GitHub

Turn low-level C FFI bindings into an idiomatic Nim API, with safer types, cleaner module boundaries, resource management, callbacks, enums, bitflags, and exception-based error handling. Use when building a high-level Nim wrapper around a C library or improving the usability of existing raw bindings.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 6 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use a two-layer design: raw FFI layer (ABI-faithful) + ergonomic Nim layer (safe, idiomatic).

    line 12
  2. Very specific:

    Use importc with cdecl (or stdcall if the library requires it).

    line 19
  3. Very specific:

    Never reorder struct fields: Use object in C field order.

    line 21
  4. Very specific:

    Use incompleteStruct and list only needed fields to reduce ABI risk.

    line 22
  5. Distinctive:

    Keep pointer types as C intends — do not convert them in the raw layer.

    line 26
  6. Distinctive:

    Do not create custom exception types unless callers handle them differently.

    line 62
  7. Very specific:

    Keep raw constant names in C style (e.g., CURLE_OK).

    line 70
  8. Very specific:

    When a C identifier collides with a Nim keyword, rename the Nim identifier and use importc: to map to the original C name.

    line 71
  9. Very specific:

    Add static: doAssert sizeof(T) == N and offsetOf checks in tests to verify struct layouts.

    line 80
  10. Distinctive:

    Test ABI with compile + link + smoke test + runtime checks.

    line 81
  11. Very specific:

    Map types: Use the type table. Verify sizes with static: doAssert sizeof.

    line 86
  12. Distinctive:

    Write ergonomic wrappers: Add destructors for owned resources (move-only or RC).

    line 88
  13. Distinctive:

    Iterate: Add missing APIs as needed.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Nim C Wrappers

Rules

Architecture

  • Use a two-layer design: raw FFI layer (ABI-faithful) + ergonomic Nim layer (safe, idiomatic). Keep the raw layer thin and stable.
  • Split modules by library domain. Mirror the C header structure for large libraries.
  • Centralize shared types in a lib_raw_types module to avoid cyclic imports.
  • Export raw symbols only for advanced users; re-export selected symbols from ergonomic modules.

Raw FFI Layer

  • Use importc with cdecl (or stdcall if the library requires it). Prefer {.push callconv: cdecl, importc.} blocks for shared conventions.
  • header declares linker-resolved imports; dynlib loads symbols at runtime. Do not combine them on one proc. Guard library names with when defined(windows): etc.
  • Never reorder struct fields. Use object in C field order. Add packed only if C headers specify packing.
  • Use incompleteStruct and list only needed fields to reduce ABI risk.
  • For C enums, use distinct integer types + const values. Do not use Nim enum in raw bindings. Find actual enum values in C headers—do not guess.
  • For bitflags, use distinct integer types with bitwise helpers. Do not use set[Enum].
  • Map C macros: numeric → const; function-like → template; use inline proc when arguments should evaluate once.
  • Keep pointer types as C intends — do not convert them in the raw layer.

Type Mapping

C TypeNim TypeNotes
charccharPlatform-dependent signedness
signed charcscharAlways int8
unsigned charuint8Safer default spelling; avoid relying on cuchar status across Nim versions
shortcshortAlways int16
unsigned shortcushortAlways uint16
intcintAlways int32
unsigned intcuintAlways uint32
longclongABI-sized (4 on Win64, 8 on LP64)
unsigned longculongABI-sized
long longclonglongAlways int64
unsigned long longculonglongAlways uint64
size_tcsize_tAlias for uint
intptr_tintPointer-sized signed
uintptr_tuintPointer-sized unsigned
floatcfloatAlways float32
doublecdoubleAlways float64
long doubleclongdoubleLimited codegen support
void*pointerUntyped
T*ptr TNullable
T**ptr ptr T
char* / const char*cstringNUL-terminated
char**cstringArrayptr UncheckedArray[cstring]

Struct types: object in C order. Fixed arrays: array[N, T]. Pointer+length: ptr T + csize_t. Raw buffers: ptr UncheckedArray[T]. Opaque handles: pointer or ptr OpaqueObj (empty object).

Ergonomic Layer

  • In =destroy, explicitly call =destroy on owned nested GC-managed fields (string, seq) after releasing C resources.
  • Define ownership hooks in the same module as the type. Cross-module hook definitions are a compile error.
  • Raise exceptions (IOError, ValueError, etc.) for C errors — do not return result wrappers that only carry ok/kind/message.
  • Do not create custom exception types unless callers handle them differently.
  • Catch errors only at translation boundaries (C return code → Nim exception, or exception → domain result). Let exceptions propagate otherwise.

Naming

  • In raw bindings, match C identifier names directly.
  • importc without an explicit string resolves the C symbol from the Nim name.
  • Strip redundant C prefixes (LIB_, foo_) in the ergonomic layer.
  • Keep raw constant names in C style (e.g., CURLE_OK).
  • When a C identifier collides with a Nim keyword, rename the Nim identifier and use importc: to map to the original C name.

Callbacks

  • Declare callbacks as plain C-callable procs such as proc onEvent(code: cint; userData: pointer) {.cdecl.}.
  • Pass closure state through userdata via rawProc/rawEnv. See references/callback_pattern.md.

Verification

  • Add static: doAssert sizeof(T) == N and offsetOf checks in tests to verify struct layouts.
  • Test ABI with compile + link + smoke test + runtime checks.

Workflow

  1. Read the C API. Identify structs, enums, functions, callbacks, and ownership semantics.
  2. Map types. Use the type table. Verify sizes with static: doAssert sizeof.
  3. Write raw bindings. One module per C header or subsystem. Centralize shared raw types to avoid cycles. Use importc, correct calling convention, packed only when C specifies it. Use typed integer aliases for enums.
  4. Write ergonomic wrappers. Add destructors for owned resources (move-only or RC). Raise exceptions for C errors. Re-export only the intended public surface. Strip prefixes.
  5. Test. Compile check → link check → smoke test → ABI sizeof/offset asserts → runtime ownership tests.
  6. Iterate. Add missing APIs as needed. Keep raw layer stable.

Common Mistakes

MistakeWhy it's wrong
Passing Nim string directly to char* parameterType mismatch; use .cstring
Using seq where C expects stable pointeradd() can reallocate, invalidating the pointer
Reordering struct fieldsBreaks ABI layout, causes garbage values
Using Nim enum for C enum valuesABI incompatibility; use typed integer aliases
Adding enum or constant values without inspecting headersFind actual enum values in C headers, do not guess
Passing closures as C callbacksC expects plain function pointers, not GC closures
Storing cstring beyond the callcstring from string.cstring dangles after the source is freed
=dup body using result = src in RC patternMay trigger implicit =copy instead of =dup; use field-by-field assignment
Wrong calling conventionCauses crashes at call sites

References

  • references/move_only_resource.md — A move-only wrapper for one owner of a C handle.
  • references/rc_resource.md — A reference-counted wrapper for shared C resource ownership.
  • references/callback_pattern.md — C callbacks with userdata, captured Nim state, and lifetime management.
  • references/enum_and_bitflags.md — Distinct-integer wrappers for non-contiguous enums and bitwise flags.
  • references/module_layout.md — Separating raw FFI from an ergonomic API in two modules.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.