Hire an AI 3D map scene developer

Everything it can hand back

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

• A scene type and 3D engine choice, with reasons
• A data check list, including coordinate system and height reference alignment
• A build order from terrain to controls
• A speed plan covering tiling, simplifying and streaming
• Lighting and starting camera settings
• An access plan and a test list for your devices

How it does the job well

• Never say the scene works, loads fast or looks right. You cannot run a browser or measure speed.
• Engine features and versions change. Mark any version-specific claim "check the engine docs".
• Do not give sizes, load times or frame rates as facts. If a figure helps, label it an example the user must measure.
• Give drafts and proposals. Get the user's go-ahead before anything that sends, publishes, spends money or changes a live system.
• 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 a terrain model or city data and want a 3D flyover on a web page.

• Brief and assumptions. The scene's job, data and devices as understood, with assumptions and MISSING items.
• Does this need 3D. A yes or no with the reason, and any part that is better in 2D.
• Scene type and engine. The scene type and 3D engine, with the reason, trade-off and runner-up.
• Data inventory. Each layer with format, size, datum check and the prep step it needs.
• Build order. Numbered steps from terrain base to labels and controls.
• Speed plan. How each layer is tiled, simplified or streamed.

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 scene's job, data, devices and access. It asks once for anything missing, then marks it MISSING.
• Check the 3D need and choose the engine. It says if 2D would do the job better, then picks a scene type and engine for your use.
• Inventory and align the data. It lists each layer and checks they share one horizontal and vertical datum.
• Plan the build order. It sets terrain base, imagery, 3D features, labels and interactions in that order.
• Plan speed. It plans tiling, simpler shapes, streaming and level of detail, so nothing loads in full.
• Plan style, camera and access. It sets lighting and a starting camera, then sets the scene private by default with a clear sign-in message.
• List the tests. It lists checks for each device, load time and the sign-in flow.

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-3d-scene-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-3d-scene-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 scene must show and the one thing viewers should learn
• Your data: terrain, buildings, imagery, 3D models or point clouds, with format and size
• The area covered, and the coordinate system and height reference if you know them
• Who views it and on what devices, such as office laptops or a wall tablet
• The 3D engine you already use, such as Cesium or ArcGIS (optional)
• Whether the scene is public or needs sign-in (optional)

Helpful context (optional)

• A list of your files with format and size, such as the first lines of a file listing.
• A screenshot of an existing scene that runs slowly.

Tools and access

• Claude, ChatGPT or Gemini: The plan works 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

• 3D map scene developer: Plan a 3D web map scene with terrain, buildings or LiDAR, lighting, camera and speed checks for Cesium or ArcGIS. Get a build plan you can follow.
  • A scene type and 3D engine choice, with reasons
  • A data check list, including coordinate system and height reference alignment
  • A build order from terrain to controls
  • A speed plan covering tiling, simplifying and streaming
  • Lighting and starting camera settings
  • An access plan and a test list for your devices
  Source: Michael Sitarzewski and Agency Agents contributors.
• 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.
• Scientific web searcher: Give it a research question and Exa access. Get meaning-based search results and extracted page text to review.
  • A ranked list of papers and pages
  • Extracted text from each link
  • Sources sorted by how scholarly they are
  • Full text of batches of URLs
  Source: K-Dense.
• 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 a terrain model or city data and want a 3D flyover on a web page.
• You have LiDAR point clouds and want people to view and measure them in a browser.
• Your 3D scene loads slowly or fails on tablets and phones.
• You must choose between Cesium and the ArcGIS JavaScript API for a 3D project.

Limits to check before starting

• You want a normal 2D web map: use the Web GIS Developer agent.
• You want to bring building models (BIM) into a map: use the BIM and GIS integration planner.
• You want to make a 3D mesh from drone photos: use the Drone mapping specialist.
• You want map colors and labels designed: 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.

• Add the pack to your AI as a skill. Or open a new chat and paste SKILL.md, then references/source-agent.md.
• Write your brief. Say what the scene shows, list each data layer with its format and size, and name the devices. Never paste real keys or passwords. Use a placeholder.
• Say 'Plan this 3D scene. Do not guess my data sizes.' Your AI asks once for what is missing.
• Read the engine choice and the question 'does this need 3D?' first. Change them if you must use a platform you already have.
• Build the scene in a test page or your GIS tool. The AI cannot run it, so test on your real devices and time the first load.
• Send back what you see, such as load time or 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-3d-scene-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.