okhp3-celestial-data

Topics in the source

• okhp3-celestial-data
• Scope
• Workflow
• 1. Plan
• 2. Validate
• 3. Execute
• Correctness notes and gotchas
• Security and boundaries

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Use the skill as a small, deterministic display-data layer. It is intentionally offline and dependency-free: do not replace the calculations with a network request, an npm package, or observatory-grade claims. | In scope | Out of scope | | --- | --- | | getMoonPhase, getAstroSeason, getMercuryStatus, getNextLunarEvents | Observatory-grade precision; target display accuracy is about ±12 hours for lunar phase | | TypeScript contracts and local UI integration | Planetary positions beyond Mercury retrograde | | Bundled 2026–2031 Mercury date table | Eclipses, solstices, equinox timestamps, natal charts, or ephemeris beyond 2031 | | Deterministic CLI checks and date-table validation | Server-side or API-backed celestial data | 1. Identify the required output and select the smallest public function set. 2. Inspect the destination types and existing imports before changing a caller. 3. Preserve these APIs and shapes: getMoonPhase(date?: Date) → { name, emoji, illumination, daysUntilNext }, with illumination as a 0.0–1.0 fraction. getAstroSeason(date?: Date) → { sign, emoji, element, dates }, with a zodiac symbol rather than a generic

This is an excerpt. Refer to the complete source and its current requirements.