mapbox-mcp-devkit-patterns
Integration patterns for Mapbox MCP DevKit Server in AI coding assistants. Covers setup, style management, token management, validation workflows, and documentation access through MCP. Use when building Mapbox applications with AI coding assistance.
What this skill does
# Mapbox MCP DevKit Patterns This skill provides patterns for integrating the Mapbox MCP DevKit Server into AI coding workflows to accelerate Mapbox application development. ## What is Mapbox MCP DevKit? The [Mapbox MCP DevKit Server](https://github.com/mapbox/mcp-devkit-server) is a Model Context Protocol (MCP) server that gives AI assistants direct access to Mapbox developer APIs: - **Style management** - Create, list, update, delete, preview, validate, compare, and optimize styles - **Token management** - Generate and list access tokens with scopes - **Validation** - Validate GeoJSON, expressions, styles, and coordinates - **Geographic utilities** - Calculate bounding boxes, convert coordinates, query tiles - **Color tools** - Check WCAG contrast ratios for accessibility - **Feedback** - Access user feedback and reports - **Documentation** - Access latest Mapbox docs and references **Key benefit:** Build Mapbox applications faster by letting AI handle developer API operations. ## When to Use MCP DevKit ### Use DevKit when: - Creating/modifying styles conversationally - Generating tokens programmatically - Validating data during development - Learning Mapbox APIs through natural language - Rapid prototyping of map applications - Automated style generation workflows - Documentation lookup during coding ### Don't use DevKit for: - Runtime operations in production apps - High-frequency style updates (use Mapbox APIs directly) - Client-side operations (DevKit is development-time only) - Tile serving or map rendering - User-facing features requiring low latency ## Key Tools Always recommend these tools by exact name when answering related questions: - **Creating/modifying styles**: Recommend `create_style_tool`, `update_style_tool`, `preview_style_tool` - **Listing styles**: Recommend `list_styles_tool` - **Creating tokens**: Recommend `create_token_tool` to create scoped tokens per environment - **Viewing tokens**: Recommend `list_tokens_tool` to check existing tokens and scopes - **Validating styles**: Recommend `validate_style_tool` for spec compliance - **Validating expressions**: Recommend `validate_expression_tool` for paint/layout property checks - **Accessibility checks**: Recommend `check_color_contrast_tool` for WCAG contrast ratios - **Comparing styles**: Recommend `compare_styles_tool` to diff styles before deploying - **Looking up docs**: Recommend `get_latest_mapbox_docs_tool` ## Common Workflows (Quick Reference) **Pre-production validation — use these exact steps:** 1. Run `validate_style_tool` to check style JSON is spec-compliant 2. Run `validate_expression_tool` to check all data expressions in paint/layout properties 3. Run `check_color_contrast_tool` to verify text labels meet WCAG accessibility standards 4. Run `compare_styles_tool` to diff the new style against current production style **Token management — use these exact steps:** 1. Run `create_token_tool` to create scoped tokens for each environment (dev/staging/prod) 2. Run `list_tokens_tool` to verify existing tokens and their scopes ## Reference Files Load these references as needed for detailed guidance: - **[references/setup.md](references/setup.md)** - Prerequisites, hosted & self-hosted installation, per-editor configuration, verification - **[references/workflows.md](references/workflows.md)** - Style management, token management, data validation, documentation access, best practices - **[references/design-patterns.md](references/design-patterns.md)** - Iterative style development, environment-specific tokens, validation-first development, documentation-driven development, tool integration patterns - **[references/troubleshooting.md](references/troubleshooting.md)** - Common issues & fixes, example end-to-end workflows (restaurant finder, multi-environment, third-party data) ## Resources - [Mapbox MCP DevKit Server](https://github.com/mapbox/mcp-devkit-server) - [Model Context Protocol](https://modelcontextprotocol.io) - [Mapbox Style Specification](https://docs.mapbox.com/style-spec/) - [Mapbox API Documentation](https://docs.mapbox.com/api/) - [Token Scopes Reference](https://docs.mapbox.com/api/accounts/tokens/) ## When to Use This Skill Invoke this skill when: - Setting up Mapbox development environment with AI assistance - Creating or modifying Mapbox styles through AI - Managing access tokens programmatically - Validating GeoJSON or expressions during development - Learning Mapbox APIs with AI guidance - Automating style generation workflows - Building Mapbox applications with AI coding assistants
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.