LuciferCore.Toolkit 1.0.5

🛠️ LuciferCore Toolkit

LuciferCore Toolkit is the official productivity companion for the LuciferCore Framework. While the Core engine focuses strictly on Zero-Allocation architecture and low-level memory primitives (Span<T>, Memory<T>), the Toolkit provides high-level abstractions and "Ease-of-Use" extensions to optimize Developer Experience (DX) without compromising the integrity of the core engine.

🌟 Why Toolkit?

The Core library is designed to be ultra-lean and dependency-free to achieve maximum throughput. However, this can sometimes make common high-level tasks repetitive. The Toolkit bridges this gap:

• Higher Productivity: Adds overloads for string, JSON, Stream, Guid, and DateTime.
• Invisible Integration: Uses the root LuciferCore namespace, allowing extensions to appear automatically on Core classes via IntelliSense.
• Modular Design: Keeps the Core engine "Pure" (Zero-Dependency). Only install the Toolkit when you prioritize convenience over absolute zero-allocation.

🚀 Installation

Install via NuGet Package Manager:

dotnet add package LuciferCore.Toolkit

Note: LuciferCore Toolkit requires LuciferCore version 1.9.7 or higher.

🛠️ Key Features

1. Buffer Productivity Extensions

Stop manually managing Span<char> or Encoding. The Toolkit allows you to work with high-level types directly:

using LuciferCore.Storage;

var buffer = new Buffer();
buffer.Append("Hello Lucifer!");     // String support via Toolkit
buffer.AppendLine("New line here."); // Automatic \n line ending
buffer.Append(Guid.NewGuid());       // Guid binary support

2. Enhanced Configuration Management

Complements the high-performance .env parser from Core with management tools:

• Auto-Reload: Automatically re-populates configurations when the .env file is modified.
• Visualizer: Prints a beautiful, color-coded configuration summary to the Console for easier debugging.

🏗️ Development Philosophy

The Toolkit strictly adheres to the "Support, Don't Interfere" principle:

1. Wrap, Don't Mutate: The Toolkit only wraps existing Core methods to create convenient overloads.
2. Explicit Performance: Be aware that some Toolkit methods may cause allocations for the sake of convenience. If you require 100% zero-allocation performance, always use the primitive methods from the Core library.

📖 Contact & Daily Activity

Stay updated with my daily research, performance benchmarks, and development journey:

• NuGet: thuangf45
• Repository: LuciferCore

👤 Author

• Nguyen Minh Thuan (thuangf45)
• Portfolio: thuangf45
• LinkedIn: thuangf45
• GitHub: thuangf45
• Blog: thuangf45
• Email: thuangf45

Pushing the boundaries of .NET performance, one buffer at a time.