Vermeil-Launcher

Work on the Vermeil companion Minecraft mod (Java/Fabric/Forge/Mixin) under companion-mod/. Use when writing or changing mod code, adding a cape/render feature, hooking the game with a Mixin or coremod, resolving mappings, or building/running the mod with Gradle. Relevant terms include fabric, forge, mixin, coremod, java, gradle, loom, forgegradle, cape, render, companion-mod, genSources, setupDecompWorkspace, runClient.

Implement or modify any feature that flows through both Modrinth and CurseForge (search, browse, install, update checks, metadata fetches). Use when touching services/modrinth.rs, services/curseforge.rs, services/cf_*.rs, commands/mods.rs, BrowseModpacks.tsx, or the Browse tab in InstanceMods.tsx. Documents the API differences between the two sources so features don't silently break for one of them.

Release a new version of Vermeil. Use when shipping, tagging, bumping versions, writing changelogs, or preparing a release. Covers the full release flow from pre-checks to tag push.

Add, update, or remove dependencies and toolchain/system prerequisites safely, covering Rust crates, npm packages, Gradle/Java mod deps, and required tools like JDK or Build Tools. Use when installing a library, bumping versions, adding a build tool, evaluating a crate, or removing unused packages. Always ripples the change into the docs that list dependencies.

Add support for a new Minecraft mod loader (like a new Forge fork or new loader project). Use when implementing a new loader backend, adding loader version fetching, or wiring a loader into the launch pipeline.

Add a new full-page screen/view to the launcher UI. Use when creating a new page, adding a new section to the sidebar, or implementing a new top-level view.

Add a new Tauri IPC command connecting the Rust backend to the SolidJS frontend. Use when creating a new invoke command, adding backend functionality, or wiring a new API endpoint through IPC.

Safely restructure, rename, extract, or move code without breaking existing functionality. Use when reorganizing modules, extracting functions, renaming symbols across the IPC boundary, or cleaning up code structure.