Karpik.Engine

Use when Codex works with Karpik.Memory, native containers, unmanaged allocation, NativeArray, NativeSlice, NativeResult, NativeLinearAllocator, NativePool, NativeArena, SimpleNativeArray migration, no-GC storage, allocation-budget tests, or memory ownership in KarpikEngine hot paths.

Use when creating, updating, reviewing, or releasing a CHANGELOG.md file, summarizing user-visible changes, or choosing the next semantic version for a release.

Dragon ECS rules for KarpikEngine. Use when Codex implements or reviews entities, IEcsComponent structs, EcsPool/EcsReadonlyPool access, EcsAspect filters, ECS systems, IEcsRun/IEcsInit/IEcsRunParallel, or ECS data layout.

Core KarpikEngine architecture rules. Use when Codex changes or reviews Client/Server/Shared boundaries, module lifecycle, Bootstrap, tick/update loops, DI, project structure, or cross-module APIs.

Real-time C# performance rules for KarpikEngine. Use when Codex works on hot paths, frame loops, ECS systems, allocation-sensitive code, cache locality, SIMD, NativeMemory, Unsafe, lock-free structures, or low-level optimization.

KarpikEngine Hot Reload rules. Use when Codex works on HotReloadHandler, IPC reload flow, IpcClient/IpcServer, PluginLoadContext, plugin assembly loading, reload-safe state, ECS state preservation, or module reload behavior.

KarpikEngine networking rules. Use when Codex works on RPC, Network.Codegen, IReader/IWriter serialization, client-server validation, IPeer, ITargetRpcSender, delivery methods, connection state, replication, prediction, or network hot paths.

KarpikEngine testing standards. Use when Codex adds or reviews unit tests, integration tests, edge-case tests, property-based tests, BenchmarkDotNet benchmarks, allocation checks, or module verification strategy.