If you're moving from Google Maps to Mapbox GL JS, this handles the translation work. It maps API equivalents (like how coordinate order flips from lat,lng to lng,lat), explains the philosophy shift from imperative objects to declarative data layers, and shows migration patterns for markers, popups, and events. The most useful bit is understanding when to use DOM-based markers versus WebGL layers. Google renders everything as DOM elements which chokes around 500+ points, while Mapbox's data-driven layers can handle thousands. Includes a seven-step migration strategy that starts with auditing your current implementation and ends with optimizations you can only do in Mapbox. Honest take: the hardest part isn't the API differences, it's rewiring your brain from objects to data sources.
npx skills add https://github.com/mapbox/mapbox-agent-skills --skill mapbox-google-maps-migration