Skip to content

TsukiNi22/ai-utils / skills/libutils/libutils

libutils

Verified

Reference of Tsukini's C++20 library libutils (namespace utils::, github TsukiNi22/libutils) - every section, header, class and public method with the version and commit hash it was generated from, how to link/include it, exceptions/error codes, verbose, and how to find what changed since. Use whenever code uses or could use libutils (utils::..., include "utils/...", find_package(utils)), when the user asks which libutils class/function does something, how to use one, or what is new in libutils, instead of searching the library sources.

FileKindSize
SKILL.mdskill md14.6 KB
reference/VERSION.mdmarkdown612 B
reference/api/algorithms.mdmarkdown10.0 KB
reference/api/arguments.mdmarkdown8.4 KB
reference/api/attribute.mdmarkdown9.0 KB
reference/api/cli.mdmarkdown5.0 KB
reference/api/concepts.mdmarkdown3.0 KB
reference/api/encapsulation.mdmarkdown9.8 KB
reference/api/exception.mdmarkdown6.7 KB
reference/api/manip.mdmarkdown10.9 KB
reference/api/math.mdmarkdown2.3 KB
reference/api/network.mdmarkdown8.4 KB
reference/api/platform.mdmarkdown6.0 KB
reference/api/pool.mdmarkdown5.1 KB
reference/api/root.mdmarkdown2.2 KB
reference/api/security.mdmarkdown8.8 KB
reference/api/system.mdmarkdown10.7 KB
reference/api/type.mdmarkdown38.5 KB
reference/api/verbose.mdmarkdown3.6 KB
reference/exception-codes.mdmarkdown7.6 KB
reference/index.mdmarkdown20.0 KB
scripts/check.shexecutablescript2.7 KB
scripts/gen_api.pyexecutablescript20.8 KB
scripts/update.shexecutablescript2.3 KB

reference/api/math.md

View on GitHub
# libutils `math`

Generated from libutils `v4.3.1` (commit `7913070`, 2026-10-22) by `scripts/gen_api.py`, do not edit by hand.

## `utils/math/MathType.hpp`

Type definition used in math computing

Namespace: `utils::math`

```cpp
// namespace utils::math
using Type = double; // Type used everywhere for coord, angle, direction, ...
using UType = std::uint64_t; // Type used everywhere for unsigned coord, angle, direction, ...
using V2Type = utils::type::OVector2<utils::math::Type>;
using Coord2D = utils::type::OVector2<utils::math::Type>;
using V2UType = utils::type::OVector2<utils::math::UType>;
using UCoord2D = utils::type::OVector2<utils::math::UType>;
using V3Type = utils::type::OVector3<utils::math::Type>;
using Coord = utils::type::OVector3<utils::math::Type>;
using V3UType = utils::type::OVector3<utils::math::UType>;
using UCoord = utils::type::OVector3<utils::math::UType>;
using Angle = utils::math::Type; // Generaly in deg
using Direction = utils::type::OVector3<utils::math::Angle>; // Generaly normalized
using Chunk = utils::type::OVector3<std::int32_t>; // Used for spacial partitionning
struct CFrame {
    utils::math::Coord position = {0.0, 0.0, 0.0}; // Coord
    utils::math::Direction orientation = {0.0, 0.0, 0.0}; // Orientation in deg
    utils::math::Direction look = {0.0, 0.0, 0.0}; // Orientation normalized
};
```

## `utils/math/geometry/Angle.hpp`

Prototype for angle computing

Namespace: `utils::math::geometry`

```cpp
// namespace utils::math::geometry
utils::math::Direction to_look(const utils::math::Direction& orientation);
```

## `utils/math/geometry/Point.hpp`

Prototype for point computing

Namespace: `utils::math::geometry`

```cpp
// namespace utils::math::geometry
utils::math::Coord2D rotate_point_2D(const utils::math::Coord2D& origin, const utils::math::Coord2D& point, utils::math::Angle angle, const bool rad = false);
utils::math::Coord rotate_point_3D(const utils::math::Coord& origin, const utils::math::Coord& point, const utils::math::Direction& orientation, const bool rad = false);
```

## `utils/math/trigo/Convertion.hpp`

Angle unit conversion (deg <-> rad)

Namespace: `utils::math::trigo`

```cpp
// namespace utils::math::trigo
utils::math::Type deg_to_rad(utils::math::Angle deg);
utils::math::Angle rad_to_deg(utils::math::Type rad);
```
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall