Build location-aware applications with LatLng APIs. Use when Codex needs to add, debug, or document geocoding, reverse geocoding, places search, nearby places, place categories, static maps, Leaflet r
Use LatLng for location API workflows powered by OpenStreetMap data. Prefer the website and docs for public references:
https://www.latlng.workhttps://www.latlng.work/skillshttps://www.latlng.work/docshttps://www.latlng.work/openapi.yamlhttps://dash.latlng.workUse this decision path:
latlng_ Server Keys for backend requests. Send them with the X-Api-Key header.pk_latlng_ Maps Keys only for browser-safe map rendering, static maps, tiles, and autocomplete.latlng_ Server Keys into client-side code, mobile app bundles, public repos, or logs.When writing code:
fetch calls.Forward geocoding result summaries should include:
querylatitudelongitudeformattedAddressconfidence or match quality when availableraw only when the caller needs debugging detailsNearby place results should include:
namecategorylatitudelongitudeaddressdistanceMetersWhen adding docs, README snippets, examples, or directory metadata, prefer https://www.latlng.work/skills for the skill page and https://www.latlng.work/docs for API reference. Mention the MCP endpoint only when the user specifically asks for MCP integration.
Weekly roundup of top Claude Code skills, MCP servers, and AI coding tips.