Stock-Back-Test-System

Enforce modern C++20 style in this repository's C++ code: prefer std types, RAII, ranges, concepts, structured bindings; ban C-style idioms (raw new/delete, C arrays, NULL, sprintf, K&R output params, plain enum, typedef). Use when writing or editing any .h / .hpp / .cpp / .cc / .cxx / .ipp file in this repo, reviewing C++ code, refactoring legacy code, or when the user mentions modern C++, C++20, lowerCamelCase, naming, or style.

Enforce clear abstraction and good OOP for C++ code in this repository: reject one-shot helpers, prefer composition over inheritance, separate interface from implementation, apply the right design pattern (Strategy, Factory, Observer, Adapter, Builder, Pimpl, Visitor, Chain, Command, Decorator) when the situation calls for it, and keep modules behind narrow public headers. Use when designing a new module, adding a new class or interface, refactoring duplicated logic, reviewing PR design choices, or when the user mentions abstraction, design pattern, refactor, OOP, interface, SOLID, or DRY.

Detect and fix performance smells in C++ code in this repository: O(n^2) loops, unnecessary copies and allocations (outside hot paths, redundant copies of small trivial types are permitted for clarity), std::map vs std::unordered_map, virtual calls and std::function in hot paths, indicator/data layer recomputation, expensive synchronization, and string concatenation inside loops. Suggest the right algorithm, container, view, or cache. Use when reviewing or writing code in tight loops (engine bar-loop, indicators, replay, data prefetch), when benchmarks regress, or when the user mentions slow, hot path, optimize, benchmark, profile, allocation, or cache.

Run and interpret the static-analysis tool stack for this repository's C++ code: clang-format, clang-tidy, clang static analyzer (scan-build), cppcheck, include-what-you-use (IWYU), and the sanitizer-instrumented dev build. Use when the user asks about static analysis, lint, tidy, sanitizers, scan-build, cppcheck, IWYU, format, warnings, .clang-tidy / .clang-format configs, or before opening / merging a pull request.

Make C++ code in this repository thread-safe and leak-free by default: enforce RAII for every resource, prefer immutable cross-thread snapshots over shared mutable state, use std::unique_ptr / std::jthread / std::scoped_lock / std::stop_token / std::atomic correctly, and run with sanitizers in dev. Use when writing or reviewing any code that touches threads, mutexes, atomics, raw pointers, manual new/delete, file handles, sockets, callbacks across thread boundaries, Qt signals across threads, or when the user mentions race, deadlock, leak, thread, async, sanitizer, or memory.