bearcove/dodeca

code-annotations

Code annotation requirements for pikru. Use when writing or porting Rust functions from C code. All ported functions must have cref comments.

codebase-layout

Codebase organization for pikru. Use when you need to find where specific functionality lives.

debugging

Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug traces in place.

git-commands

Git command conventions for pikru. Use when running any git commands to avoid blocking on interactive pager.

idiomatic-rust

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.

subtest-isolation

Create minimal subtests to isolate and fix complex bugs. Use when a test fails and the issue is buried in complexity.

testing

Testing conventions for pikru. Use when running tests to avoid timeouts. DO NOT run the full test suite.