القائمة
Code annotation requirements for pikru. Use when writing or porting Rust functions from C code. All ported functions must have cref comments.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Codebase organization for pikru. Use when you need to find where specific functionality lives.
Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug traces in place.
Git command conventions for pikru. Use when running any git commands to avoid blocking on interactive pager.
Idiomatic Rust patterns for pikru C port. Use when writing or reviewing Rust code ported from C. Don't write C in Rust - the goal is correct behavior, not line-by-line translation.
Create minimal subtests to isolate and fix complex bugs. Use when a test fails and the issue is buried in complexity.
Testing conventions for pikru. Use when running tests to avoid timeouts. DO NOT run the full test suite.
| name | code-annotations |
| description | Code annotation requirements for pikru. Use when writing or porting Rust functions from C code. All ported functions must have cref comments. |
All Rust functions ported from C must be annotated with a cref comment:
// cref: c_function_name
fn rust_function() { ... }
The // cref: comments create a traceable link between the Rust implementation and the original C function it was ported from. This helps: