Zinit is a Zsh plugin manager that provides fast, asynchronous (turbo) loading of plugins and snippets with a unique ice modifier system for declarative configuration. The architecture is a monolithic shell-script library with the primary entry point `zinit.zsh` sourced from `.zshrc`. Key subcommands include `load`, `light`, `snippet`, `update`, `delete`, `compile`, and `unload`. The ice modifiers allow transient options like `wait`, `atclone`, `atpull`, `make`, and `extract` to control how plugins are fetched, compiled, and sourced. The project uses an annex system for extensibility and includes comprehensive completion management, reporting, and diff tracking. The codebase is written entirely in Zsh and relies on common Unix tools (git, curl, tar, etc.). While not a general-purpose application, it is a well-crafted tool for Zsh users, with reusable standalone utilities like `share/git-process-output.zsh` and `share/rpm2cpio.zsh`. The test infrastructure (`tests/_support/bootstrap`) provides a sandbox pattern for integration testing Zsh plugins.
BepInEx is a plugin/modding framework for Unity (Mono and IL2CPP) and .NET games (XNA, FNA, MonoGame). It injects itself into a game process via Doorstop, runs a preloader that patches game assemblies, and then loads user-authored plugins through a chainloader. The framework provides a comprehensive infrastructure: thread-safe configuration (TOML-based), structured logging (console, disk, Unity log), assembly patching API, native detour abstraction (Dobby/Funchook), and interop generation for IL2CPP games (via Cpp2IL and Il2CppInterop). It supports Windows, Linux, and macOS (with limitations), and handles multiple Unity runtime variants and .NET Framework/Core. The architecture is modular: core libraries (`BepInEx.Core`, `BepInEx.Preloader.Core`) provide the base plugin contract, configuration, logging, and assembly scanning; runtime-specific projects (`BepInEx.Unity.Mono`, `BepInEx.Unity.IL2CPP`, `BepInEx.NET.*`) implement the platform-specific startup, patching, and integration. External dependencies include HarmonyX for runtime method patching, MonoMod for assembly manipulation, and SemanticVersioning for dependency resolution. While many components are tightly coupled to the game-modding domain, several subsystems—logging, configuration, topological sorting, native detours—are well-abstracted and potentially reusable in other C# host applications. The codebase shows signs of long-term evolution (deprecated methods, duplicated `KeyboardShortcut` classes, static singletons) but remains actively maintained with recent commits and responsive issue triage.