bearcove

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

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.

Styx configuration language syntax and schema reference. Use when writing or editing .styx files, creating schemas, or debugging syntax errors. Covers syntax (scalars, objects, sequences, tags, heredocs), schema language, and CLI validation.

Styx configuration language syntax and schema reference. Use when writing or editing .styx files, creating schemas, or debugging syntax errors. Covers syntax (scalars, objects, sequences, tags, heredocs), schema language, and CLI validation.

Lead agent for cooperative work over tmux. Use when assigning tasks to another agent, coordinating multi-agent work, or when the user mentions mate, captain, agent collaboration, or tmux-based coordination.

Worker agent skill for cooperative work over tmux. This skill is activated when you receive a task from the captain via mate assign. Follow these instructions for how to work, report progress, and what to avoid.

Add proper Tracey spec annotations to code, find requirements, and check coverage. Use when working with projects that have Tracey configuration (.config/tracey/config.styx), when adding spec references to code, or when checking requirement coverage.

Profile a program with stax (live CPU stacks, off-CPU waits, target/GPU spans, annotated disassembly) to find where time actually goes. Use whenever you need to measure performance, find hot functions, or answer "why is this slow" instead of guessing. Covers…