breenix-interrupt-syscall-development

Interrupt and syscall handlers must eliminate logging and diagnostic code to preserve real-time behavior. This Skill enforces strict prohibitions on debug output and memory allocations in these hot paths, replacing them with external tracing methods that don't interfere with deterministic execution.

Deterministic interrupt handlers require minimal, allocation-free code with no logging or memory diagnostics. This Skill provides approved patterns and code-review checklists to ensure handlers stay lightweight and predictable, critical for systems where timing guarantees matter.

Standard debugging tools like debug prints and memory diagnostics break real-time behavior in syscalls and interrupts. This Skill guides you to replace them with external tracing methods and testing patterns that gather diagnostic data without impacting the hot path.

Safe interrupt handler patterns avoid allocations, logging, and memory diagnostics entirely. This Skill documents approved minimal patterns and provides a code-review checklist to enforce these constraints during development.

Testing interrupt handlers requires methods that don't introduce diagnostic overhead into the hot path. This Skill covers testing strategies and code-review guidance that validate correctness while preserving deterministic behavior.