If you've configured GitHub Packages, you can just:
> dotnet add PROJECT package StirlingLabs.Utilities
or just use NuGet however you would normally.
Any stand-alone code that is used in more than one package is a contender to be included here. If you see something that you think should be included, please create an issue or PR so we can discuss it.
This should be the first place that common code is generalised. If it turns out that the implementation should be separated for some reason (licensing or some other optimisation) then it should be fully moved to the new package and then included back here via NuGet. Users of Utilities.Net should not have to change their code during this process (if namespaces absolutely have to be modified, provide aliases).
If the reason for separating a module out ends, it should be moved back into Utilities as soon as it can be safely achieved (and the unecessary repo archived). At no point should there be two code repositories being maintained; a single source of truth must exist at all times.