latitude-zone-math-authority

Defines canonical latitude band calculations for the Latitude game mod.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/joolbits/latitude --skill latitude-zone-math-authority
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: latitude-zone-math-authority
Source: https://github.com/joolbits/latitude/tree/main/.windsurf/skills/latitude-zone-math-authority
Command: npx skills add https://github.com/joolbits/latitude --skill latitude-zone-math-authority

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures all systems within the Latitude mod use consistent mathematical calculations for determining geographical zones and their associated properties, preventing bugs and inconsistencies.

Core Features & Use Cases

  • Unified Zone Calculation: Provides a single source of truth for calculating latitude bands (Equator, Tropical, Temperate, Polar, etc.) based on world radius and player position.
  • Consistent Thresholds: Prevents duplication of threshold logic across different game systems like world generation, guards, fog, hazards, and the HUD.
  • Use Case: When a player encounters unexpected snow in a temperate zone, this Skill's authority can be consulted to verify the correct zone calculation and identify any discrepancies in the warm/cold band predicates.

Quick Start

Consult the latitude-zone-math-authority skill to determine the correct latitude zone for the player's current position.

Frequently Asked Questions about latitude-zone-math-authority

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep latitude zone calculations consistent across different game systems?

Latitude zone calculations stay consistent by enforcing a single source of truth for radius, normalized latitude, and zone thresholds across all game systems, preventing duplicated logic and bugs.

Why does my game generate unexpected snow in a temperate zone?

Unexpected snow in a temperate zone happens when game systems hardcode warm or cold band predicates instead of consulting a canonical latitude math authority to verify correct zone mapping and thresholds.

What is a normalized latitude value used for in world generation?

A normalized latitude value determines a player's geographical zone by mapping world radius and position into consistent latitude bands, ensuring worldgen, fog, and hazards apply correct environmental effects.

How do I stop duplicated zone threshold logic in my game mod?

Stop duplicated zone threshold logic by mandating a single-source-of-truth implementation for zone mapping, sea level, and warm or cold band predicates, while forbidding hardcoded values across game systems.

Can I hardcode latitude band thresholds for specific game mechanics like guards or HUD?

Hardcoding latitude band thresholds for guards or HUD is forbidden to prevent inconsistencies; all game systems must derive warm or cold band predicates and sea level from the canonical math authority.