Mapbox Agent Skills

Setup work, one codebase at a time: Mapbox GL JS inside React, Vue, Svelte or Angular; the Maps SDK in Swift and SwiftUI; the same in Kotlin and Jetpack Compose; a Flutter route that covers both phones from one codebase. Arriving from Google Maps or MapLibre belongs here too, because that is the same job with somebody else's code already in the way.

Anything with a location in the question, and which call answers it: a named shop against a type of place nearby, how far apart two points are on the road rather than on the map, whether a point falls inside a delivery area. The shop-finder screen that puts all of that behind a list and a map is here as well.

The appearance of the map itself — what colour water, roads and parks are, which labels survive as the reader zooms out, which layer recipe suits a property site or a delivery tracker — and how your own figures go on it as shaded regions, heat or height rather than a pin per row.

The pass over a map that is nearly finished: whether the style file is valid and its lettering still readable against what sits behind it, what makes it slow to appear or stutter once it holds thousands of markers, and what to do about an access key that any visitor can read out of the page.

The two arrangements where something else drives Mapbox instead of a person: an assistant in the editor doing it while you talk to it, and a finished product of your own reaching Mapbox through an agent framework. The third skill here is about making those answers carry the source they came from.