Cursor rule

1---
2description: 
3globs: 
4alwaysApply: true
5---
6 
7 
81. prefer one class per file.
92. use Google C++ coding styles.
103. make classes immutable as much as possible.
114. follow guidelines of effective modern c++.
12 
13 
14Name methods (casing, etc) like "is_valid", "stream_text"
15 
16Lean on auto. Let the compiler deduce obvious types and keep code DRY. 
17 
18Use nullptr, never 0 or NULL. A unique keyword prevents overload ambiguities and makes pointer intent explicit. 
19 
20Express ownership with smart-pointers (std::unique_ptr, std::shared_ptr, std::weak_ptr). Raw pointers say nothing about lifetime. 
21 
22Move more, copy less. Pass/return by value when cheap-to-move; use std::move to convey transfer of resources. 
23 
24Mark intent with keywords (const, constexpr, noexcept, override, delete). They document guarantees and enable optimisations. 
25 
26Prefer brace initialisation. It prevents narrowing, works with std::initializer_list, and unifies syntax. 
27 
28Capture carefully in lambdas; avoid default capture ([=], [&]). Explicit captures beat accidental lifetime bugs. 
29 
30Think tasks, not threads. Launch work with std::async, std::future, or std::packaged_task; join or detach thoughtfully. 
31 
32Use std::atomic for inter-thread data, not volatile. Atomics give ordering guarantees; volatile is for hardware registers. 
33 
34Emplace instead of insert / push_back. Construct elements in place to avoid extra moves or copies.