What problem does it solve? Contributors editing the gcl-core paths, config, instances, or settings modules need to know the exact on-disk layout and invariants of the launcher's data model, or they risk corrupting config.toml, instance.toml, or options.txt files. ## Core Features & Use Cases - Root and config layout: Explains GCL_ROOT resolution, the root redirect pointer, and the config.toml schema including JVM defaults and game_defaults preseed. - instance.toml schema: Documents every field including pack source, JVM block, settings_overrides, and content entries with source, kind, and enabled state. - GC preset semantics: Covers GcPreset parsing, lenient aliases, Java-version folding of zgc to zgc_generational, conflict detection with extra JVM args, and probe caching. - options.txt layering: Details the colon-separated format, preseed versus override behavior, the settings catalog, and the Override > File > Preseed > Default merge order. - Use Case: Before adding a new per-instance JVM field, read this Skill to learn that set_instance_jvm must preserve the saved GC preset and that all writes under the root must go through paths::write_atomic. ## Quick Start Read this Skill before modifying any code under gcl-core paths/, config/, instances/, or settings/ to learn the file formats and invariants you must preserve.