map-geocoding-debug
SkillProductivityPetSwipe map and geocoding workflow for diagnosing map page issues, geocode request volume, cache behavior, API proxy behavior, CORS issues, and location-related UI regressions. Use when the task mentions the map page, geocoding, location results, or geocode performance.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the map-geocoding-debug skill
What this skill tells your AI
The instructions your AI receives, as published by hoangsonww/petswipe-match-app in .agents/skills/map-geocoding-debug/SKILL.md and read by ahel’s review.
Use this skill for map and geocoding issues.
Workflow
- Start from
frontend/pages/map.tsx. - Trace how location strings are generated, normalized, cached, and rendered.
- Check whether the frontend is calling the local proxy or an external geocoder directly.
- Check request amplification, duplicate queries, fallback queries, and cache-miss behavior.
- Validate any fixes without introducing responsive or chart-like overflow regressions on the page.
Repo-Specific Guidance
- The map page and the frontend geocode API route are the primary touchpoints.
- Request explosion and low-signal fallback queries are a known class of issue in this repo.
- CORS or upstream slowness should be treated separately from local query-generation bugs.
If the issue is large, spawn map_debugger first.
Read references/map-debug-checklist.md.
Signals
- GitHub stars
- 26
- Forks
- 12
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
map-geocoding-debug- Source
- github.com/hoangsonww/petswipe-match-app