What problem does it solve? When working on the gcl-core download and HTTP modules of this Minecraft launcher, you need to understand how files are fetched, verified, cached, and deduplicated so you do not break invariants like streaming caps, hash checks, or redirect guards. ## Core Features & Use Cases - Content-addressed cache: Every download lands in cache/objects/<sha1> and is hard-linked to its final path, so Modrinth and CurseForge copies of the same jar are stored once. - Verified streaming downloads: SHA-1 and size are checked while streaming, partial files use unique .part staging names, and mismatches trigger bounded retries before a hard error. - Media caches with security policies: Icon and description-image caches enforce HTTPS-only schemes, host allowlists, private-IP refusal, redirect re-validation, byte caps, and LRU-style pruning. - Use Case: Before modifying gcl-core/src/download/ or http/, load this Skill to learn why downloads must stream (never buffer whole files), why retries skip 404/403, and how the redirect guard re-checks the allowlist on every hop. ## Quick Start Ask the assistant to explain or modify the download queue, cache, or icon fetching logic in gcl-core using the download-cache conventions.