latitude

Read-only analyzer for Latitude atlas and headless proof artifacts. Use when you have atlas or report outputs and need a structured audit of what looks wrong, what category of wrong it is, and whether the evidence suggests real worldgen regression versus validator or viewer/report drift. Do not use for rerunning jobs, rebuilding, file modification, or multi-fix brainstorming.

Read-only Git diff explainer for changelogs, PR summaries, slice review, and scope checks. Use when you need plain-English explanations of working tree diffs, staged diffs, or comparisons between two refs, with subsystem grouping and risk/scope assessment. Do not use for commit, tag, push, stash, checkout, rebase, reset, or file modification.

Read-only triage assistant for worldgen and system regressions. Use when a symptom needs to be mapped to the most likely pipeline stage and reduced to exactly one narrow next slice, especially for biome placement, seams, atlas output, or unclear bug location. Do not use for code changes, multi-fix brainstorming, or broad debugging spirals.

Read-only pre-flight guard before using the savepoint skill. Use when deciding whether the current Git repo is safe and narrow enough for a one-slice savepoint, with a clear safe-or-stop decision based on repo root, branch, HEAD, staged and unstaged changes, and generated junk. Do not use for commit/tag/push, stash, reset, cleanup, branch surgery, or conflict resolution.

Create Git savepoints after a successful change: show status, interactively stage intended hunks, commit with a concise slice summary, tag as save/slug, push commit and tag, then report branch+hash+tag. Use when you need a fast rollback point or to checkpoint a completed slice.

Read-only workspace hygiene checker for Git repos. Use when repo state feels cluttered, before handoff, savepoint, or release hygiene, or when you need to distinguish runtime junk, generated files, temp world files, and machine-specific clutter from real source edits. Do not use for deletion, git clean, reset, stash automation, or .gitignore edits.

Safe Git-based workspace handoff for the same repo between a Mac and a laptop. Use only for leave-this-machine, arrive-on-other-machine, and safe-sync-status checks when switching devices and you need to inspect repo state, preserve uncommitted work, and sync safely without force-pushes or hard resets.

Authoritative list of all vanilla Minecraft biomes and the latitude bands they are allowed to generate in for the Latitude (Globe) mod. This skill forbids guessing, omission, or reassignment of biomes and serves as the single source of truth for biome inclusion and climate eligibility.

Defines the contract between vanilla “base” biomes and Latitude “out” biomes. Prevents incorrect assumptions about F3 biome, temperature/precip flags, and feature placement. Provides the required debugging interpretation for LAT_PICK logs.

Step-by-step playbook for backporting Latitude changes across MC 1.21.x targets (e.g., 1.21.11 -> 1.21.1). Enforces one-variable-at-a-time, cherry-pick discipline, minimal tests, version/tag correctness, and prevents branch/build confusion.

Rules for adding debug logs, counters, overlays, and sanity pings in Latitude. Enforces gated, minimal, removable instrumentation and forbids permanent spam in hot paths.

Canonical rules for how Latitude decides biomes and applies them across generation stages. Prevents the model from inventing steps, reordering pipeline stages, or “fixing” bugs by changing generation order.

Authoritative “promise of Latitude” rules. Encodes the non-negotiable player-facing behaviors (climate continuity, band logic, no warm-band snow, intuitive exploration). Prevents technically-correct changes that break the mod’s feel.

Release guardrails for Latitude. Prevents tagging/building/uploading from the wrong branch, mismatched version strings, dirty working trees, or shipping dev/debug artifacts. Enforces one-step-at-a-time release checklist.

Rendering rules for Sodium/Iris compatibility in Latitude (E/W storm walls, fog, overlays). Forbids raw GL state, mandates entry-based vertex emission, approved RenderLayers, and shader-safe debugging patterns.

Repo hygiene rules for Latitude. Prevents generated/extracted artifacts from entering commits, release branches, tags, or jars. Provides the canonical ignore list and cleanup commands.

Rules for when Latitude UI screens and HUD overlays may render or open. Prevents screens auto-opening in-world, enforces debug gating, and codifies “world creation only” flows.

Canonical debugging + fix strategy for “wrong blocks in the wrong place” bugs. Forces evidence-first identification of the write path and mandates minimal, choke-point fixes (feature cancel / ChunkRegion / ProtoChunk). Forbids guessing via biome reassignment or pipeline invention.

Canonical authority for Latitude band math (radius, t, thresholds, and helpers). Prevents hardcoding, duplicated thresholds, or inconsistent warm/cold checks across worldgen, guards, fog, hazards, HUD, and features.