Hire an AI web GIS developer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A mapping library choice with reasons
• A data plan: tiles, clustering and filters
• An interaction and layout plan for desktop, tablet and phone
• A live data plan, if you need one
• Code sketches, marked as drafts you have not run
• Speed and phone checks to run
• Open questions

How it does the job well

• Never say the map works or is fast. You cannot run a browser or measure speed.
• Library features and versions change. Mark any version-specific claim 'check the library docs'.
• Give drafts and proposals. Get the user's go-ahead before anything that sends, publishes, spends money or changes a live system.
• Keep sample numbers and templates labelled as examples. Never state an invented figure as a result.
• Agree the question and the decision it supports before analysing.
• Check the data first: date range, grain, missing values, duplicates and definitions.
• Compare like with like: same period length, definitions and segments.

Mistakes it avoids

• Reporting a change without checking whether tracking or definitions changed.
• Treating correlation as cause.
• Averages that hide important segments or outliers.

What a good result looks like

An example, not your task: You have location data and want an interactive map on your website.

• Brief and assumptions. The map's job, data and devices as understood, with assumptions and MISSING items.
• Library choice. The mapping library, the reason, the trade-off and a runner-up.
• Data and tiles. For each layer, whether it is served as tiles, clustered or filtered, and why.
• Interactions and layout. Each feature on desktop and phone, with the loading state and legend.
• Live data. How updates arrive and how the map shows them, when you need it.
• Performance checks. Numbered checks for phones, slow connections and large layers, with what a pass looks like.

How the work is checked

• Numbers reconcile to the source totals, and the reconciliation is shown.
• Every chart and number states its source, period and definition.
• Limits and next checks are listed.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Collect the brief. It confirms the map's job, the data, the devices and any live feed or sign-in. It asks once for anything missing, then marks it MISSING.
• Choose the library. It compares the options for your use case and says why one fits, using the profile's guide.
• Plan the data. It plans vector tiles, clustering, viewport filtering and simpler shapes so the map never loads every feature.
• Plan interactions and layout. It plans pan, zoom, identify, search, legend and loading state, for phones, tablets and desktops.
• Plan live data. If needed, it plans how updates arrive and show without a page reload.
• List the checks. It lists tests for phone use, slow connections and large layers, and what is still unknown.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id gis-web-gis-developer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/gis-web-gis-developer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• What the map should show and let people do, such as search, identify or measure
• Your data: type, format and size, such as 20,000 points in GeoJSON
• Who uses the map and on what devices
• The library or platform you already use, such as ArcGIS (optional)
• A live data source, such as a WebSocket or an API (optional)
• Sign-in needs, such as ArcGIS sign-in or API keys (optional)

Helpful context (optional)

• A sample of your data, such as the first 20 rows or the file sizes.
• A screenshot of your current map and any console errors.

Tools and access

• Claude, ChatGPT or Gemini: The plan and code sketches work from a pasted profile and your brief.
• Claude Code: It can read your project and data files, so the plan fits your real layers.

Functions and deliverables

• Web GIS developer agent: Plan an interactive web map. Get the mapping library choice, data and tile plan, and mobile and speed checks for MapLibre, Leaflet or ArcGIS.
  • A mapping library choice with reasons
  • A data plan: tiles, clustering and filters
  • An interaction and layout plan for desktop, tablet and phone
  • A live data plan, if you need one
  • Code sketches, marked as drafts you have not run
  • Speed and phone checks to run
  • Open questions
  Source: Michael Sitarzewski and Agency Agents contributors.
• Mobile app designer: Share the platform, app flow and device needs. Get a touch-first design, feasibility review and device checks to run.
  • A risk score with a reason for each of the five points
  • A touch-first layout with the main action in thumb reach
  • Notes on what differs between iOS and Android
  • Loading, error and no-signal states
  • What to simplify first, if the score is low
  Source: sickn33.
• Shopify theme developer: Say how your store should look. Get a built or edited theme with sections, templates and speed fixes.
  • Theme files: sections, templates and snippets
  • Theme editor settings
  • Local setup steps
  • Speed fixes
  • Deploy steps
  Source: dragnoir.
• 3D web scene builder: Share a scene brief, web framework, model files and target devices to get 3D scene code with a loading state and a fallback.
  • A working 3D scene as code
  • A tool recommendation with reasons
  • Loading and fallback handling
  • Controls tuned for first-time users
  • A performance checklist
  Source: sickn33.
• Metric definition writer: Share a metric, calculation and business use. Get a YAML definition, validation results and questions for the data owner.
  • A filled metric, dimension or entity YAML
  • A validation report
  • dbt-ready field names
  • Notes on edge cases
  Source: Nimrod Fisher.

Tasks you can use it for

• You have location data and want an interactive map on your website.
• Your map freezes or crawls with thousands of points.
• You must choose between MapLibre, Leaflet and the ArcGIS JavaScript API.
• You need live data on a map, such as vehicles or sensors.

Limits to check before starting

• You need desktop GIS analysis or a map for print: use the GIS analyst.
• Your data is messy and needs cleaning or converting first: use the Spatial Data Engineer agent.
• You need 3D scenes or terrain: use the 3D map scene developer.
• You need map colors, labels and basemap design: use the Map designer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack and add it as a skill in your AI. Or paste SKILL.md into a new chat, then paste references/source-agent.md after it.
• Write your brief: what the map shows, your data type and size, who uses it and on what devices. Never paste real API keys. Use a placeholder.
• Say 'Plan this web map. Do not guess my data size.' Your AI asks once for what is missing.
• Read the library choice and data plan first. Change them if you must use a platform you already have.
• Build the sketches in a test page. The AI cannot run your map, so test on a real phone and a slow connection yourself.
• Bring back what you see, such as load time or console errors, and ask for fixes.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/gis-web-gis-developer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.