taedlar/neolith

unit-test

Add unit tests for individual components. Use the GoogleTest (GTest) framework to define test cases and assertions. Troubleshooting test failures involves checking test logs, reproducing failures locally, and debugging with breakpoints or additional logging…

원문 언어: 영어

function-naming

Validates function naming when adding new functions, refactoring existing functions, or reviewing function signatures.

원문 언어: 영어

lpc-coding

Generate and refactor Neolith LPC code with correct driver semantics. Use when writing LPC functions, efun calls, simul_efun-aware code, inheritance calls, strict_types-safe code, inline LPC code (pre_text) in unit-tests, or when prompts mention ambiguity…

원문 언어: 영어

build-options

Manage Neolith build-time options: add, change, or remove CMake options that control driver behavior and LPC visibility. Use when creating a new option, toggling an existing option default, renaming macros, tracing how an option surfaces to LPC code, or…

원문 언어: 영어

async-worker-pattern

Implement async worker thread patterns with bounded task queues, admission control, and completion posting. Use when adding blocking I/O operations (DNS, file I/O, network calls) that must not block the main event loop. Covers worker thread design, queue…

원문 언어: 영어

trace

Add opt_trace() calls for debugging and profiling. Use -t option to enable specific trace tiers and levels.

원문 언어: 영어