Add MapLibre-Mapbox interoperability skill #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Provides guidance for using Mapbox services (vector tiles, Search JS, Geocoding, Directions, Isochrone APIs) with MapLibre GL JS renderer. This hybrid architecture approach lets developers keep their open-source MapLibre renderer while leveraging Mapbox's premium data and services. Key patterns covered: - MapLibre rendering + Mapbox vector tiles - MapLibre + Mapbox Search JS (no backend needed) - MapLibre + Mapbox APIs (Geocoding, Directions, Isochrone) Benefits: - Keep open-source renderer (BSD license) - Access premium Mapbox data/services - Cost optimization (free renderer + pay-per-use APIs) - No infrastructure management Includes: - Architecture patterns for each integration type - Token management and security best practices - Complete integration example (restaurant finder) - Cost optimization strategies - Framework integration patterns (React, Vue, etc.) - AGENTS.md quick reference Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
This was referenced Feb 3, 2026
Addresses feedback that interop skill was missing the important use case of using Mapbox Tiling Service to process, host, and serve custom vector tilesets. Changes: - Added Pattern 4: MapLibre + Mapbox Tiling Service - Shows how developers can upload custom data to MTS - Explains MTS workflow: upload → process → host → consume - Highlights infrastructure benefits (no tile processing, hosting, CDN) - Added MTS to "What You Can Use" tables in both SKILL.md and AGENTS.md - Included example use cases: real estate, store locators, delivery zones - Added links to MTS resources (Studio, Tilesets API, CLI) This pattern complements the existing basemap tiles pattern by showing how to handle large custom vector tilesets using Mapbox infrastructure with MapLibre rendering. Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Resolves conflict in cspell.config.json by keeping both geospatial and googlemaps.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds new skill showing how to use Mapbox services WITH MapLibre GL JS (hybrid architecture).
What This Skill Does
Shows MapLibre GL JS users how to leverage Mapbox's premium services while keeping their open-source renderer:
Key patterns:
Benefits of hybrid approach:
Contents
File:
skills/mapbox-maplibre-interop/Use Case
This skill is for MapLibre users who want to:
Complements the
mapbox-maplibre-migrationskill by offering an alternative to full migration.Testing
🤖 Generated with Claude Code