Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Review the boundary between [calling language] and [native library]. Use the documented signature to identify type widths, encodings, buffer sizes, calling conventions, ownership transfers, release operations, and error reporting. Inspect asynchronous callbacks and borrowed-memory lifetimes. Build a focused wrapper that validates the contract and maps errors clearly. Check normal, empty, oversized, invalid, and repeated-allocation cases using available diagnostics. Report the tested platform and configuration, concrete lifetime risks, and any compatibility assumptions that still need evidence.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Rust Reference — External blocks and ABI declarations
- Python — Foreign function calls with ctypes
- Rust Book — Ownership, stack, and heap
Documentation links checked .
Editorial review · October 28, 2026
Limited: Original instructional template; not executed. FFI audit prompt is an original verification procedure; platform compatibility and memory checks were not executed.