تشغيل أي مهارة في Manus بنقرة واحدة

$pwd:

cesium-agents-scene-architect

Name: Cesium Agents Scene Architect
Author: Impertio-Studio

// Use when starting a new CesiumJS application or feature and deciding how to structure the scene: which viewer class, which imagery and terrain, how to represent a dataset, and whether to enable on-demand rendering. Prevents the wrong-API-tier choice (Entity where 3D Tiles is needed, or the reverse), the continuous-render battery drain, and missing-token blank globes. Orchestrates the CesiumJS skill set into one setup decision path. Keywords: CesiumJS architecture, how do I structure a Cesium app, which viewer, Viewer or CesiumWidget, Entity or Primitive or 3D Tiles, choose imagery provider, choose terrain provider, requestRenderMode, scene setup decision, how do I display my data in Cesium, what API should I use, getting started Cesium scene, plan a Cesium scene.

تشغيل في Manus

$ git log --oneline --stat

stars:١

forks:٠

updated:٢٠ مايو ٢٠٢٦ في ٠٧:٤٤

مستكشف الملفات

4 ملفات

SKILL.md

readonly

related-skills.json

نفس المستودع

cesium-agents-skill-validator.md

from "Impertio-Studio/CesiumJS-Claude-Skill-Package"

Use when CesiumJS code has just been generated or reviewed and must be checked before it is called done, to catch deprecated APIs and common defects, or when auditing CesiumJS code from an older source. Detects the removed synchronous patterns (readyPromise, the url constructor option, ModelExperimental, defaultValue, new on a Cartesian factory), WebGPU assumptions, missing ion tokens, missing destroy() calls, and coordinate-type mistakes. Runs a deterministic checklist and routes each failure to the skill that fixes it. Keywords: validate CesiumJS code, review Cesium code, is this Cesium code correct, deprecated CesiumJS API, readyPromise, ModelExperimental, defaultValue removed, check before commit, CesiumJS code quality, lint Cesium, did I use the right API, audit Cesium scene, why might this code fail.

2026-05-201

cesium-errors-coordinates.md

from "Impertio-Studio/CesiumJS-Claude-Skill-Package"

Use when CesiumJS geometry renders in the wrong place, falls through the terrain, sits at the center of the Earth, or never appears, and when position values come back as NaN. Prevents the radians-versus-degrees mistake, the Cartographic-versus-Cartesian3 mixup, the longitude and latitude swap, the GeoJSON ground-clamp surprise, and terrain-clamping before terrain has loaded. Covers Cartesian3, Cartographic, the fromDegrees factories, HeightReference, HeadingPitchRoll conventions, and terrain height sampling. Keywords: CesiumJS coordinates, NaN position, entity not showing, model wrong place, geometry at center of earth, off the globe, radians degrees, longitude latitude swapped, Cartographic Cartesian3, fromDegrees, fromRadians, clampToGround, sampleTerrainMostDetailed, HeightReference, HeadingPitchRoll, heading pitch roll wrong, why is my point underground, how do I place something on terrain, position is NaN.

2026-05-201

cesium-errors-memory.md

from "Impertio-Studio/CesiumJS-Claude-Skill-Package"

Use when a CesiumJS app's memory keeps growing, the browser tab slows down or crashes after running a while, or the console reports "Too many active WebGL contexts" or "DeveloperError: This object was destroyed". Covers WebGL resource leaks from missing destroy() calls, teardown ordering, reusing primitives after destruction, entity-removal memory retention, lost-reference bugs that only look like leaks, and exhaustion of the browser 16-context WebGL budget by single-page-app routing or React re-mounts. Keywords: memory leak, heap grows, tab crash, out of memory, browser freezes, app slow over time, WebGL context lost, too many active WebGL contexts, This object was destroyed, DeveloperError, destroy, isDestroyed, PrimitiveCollection, destroyPrimitives, viewer.destroy, how do I clean up a Cesium viewer, why does my Cesium app leak memory.

2026-05-201

cesium-errors-rendering.md

from "Impertio-Studio/CesiumJS-Claude-Skill-Package"

Use when a CesiumJS globe renders blank, black, white, or frozen, when the canvas shows nothing, when the WebGL context is lost, or when a render-loop error panel covers the canvas. Prevents the blank-globe trap caused by an unset CESIUM_BASE_URL, a missing or invalid Cesium ion token, or an omitted bundler asset-copy step. Covers the renderError event, WebGL context-loss recovery, the 16-context budget, and missing imagery or terrain. Keywords: blank globe, black screen, white screen, nothing renders, globe not showing, CESIUM_BASE_URL, CONTEXT_LOST_WEBGL, renderError, rethrowRenderErrors, Ion.defaultAccessToken, HTTP 401, webglcontextlost, too many active WebGL contexts, no imagery, no terrain, how do I fix a blank Cesium globe.

2026-05-201

cesium-errors-tileset.md

from "Impertio-Studio/CesiumJS-Claude-Skill-Package"

Use when a Cesium3DTileset does not load or render: the console floods with CORS errors, the network tab shows 401 or 403, readyPromise is undefined, fromUrl resolves but nothing appears, the tileset has holes, or fromUrl rejects with a RuntimeError. Covers CORS and file protocol failures, ion and Google authentication, the removed synchronous readyPromise construction, invisible tilesets, individual tile failures, and unhandled promise rejections. Keywords: Cesium3DTileset, fromUrl, fromIonAssetId, tileset not loading, 3D Tiles not showing, CORS error, blocked by CORS policy, file protocol CORS, 401 tileset, 403 Forbidden, tiles missing, holes in tileset, tileFailed, readyPromise is undefined, RuntimeError, unhandled promise rejection, GoogleMaps defaultApiKey, Ion.defaultAccessToken, why is my tileset blank, how do I load 3D Tiles, how do I fix a CORS error.

2026-05-201

cesium-impl-aec-georef.md

from "Impertio-Studio/CesiumJS-Claude-Skill-Package"

Use when placing a BIM model, CAD model, IFC export, or city model into a CesiumJS globe at its real geographic location, and the model renders at the center of the Earth, sits at the wrong place, floats above or sinks below terrain, or faces the wrong direction. Prevents the identity-modelMatrix mistake (a model with no transform draws in raw ECEF coordinates), the double-transform mistake (re-placing an already-georeferenced ion tileset), the radians-versus-degrees HeadingPitchRoll mistake, and the conversion-pipeline-is-an-API mistake. Separates the official CesiumJS georeferencing API (Transforms, Matrix4, HeadingPitchRoll, modelMatrix) from the external CityGML and IFC conversion workflow. Keywords: CesiumJS AEC, georeference, georeferencing, BIM in Cesium, IFC in Cesium, CityGML, modelMatrix, Transforms.eastNorthUpToFixedFrame, headingPitchRollToFixedFrame, HeadingPitchRoll, Matrix4, ECEF, local frame, east north up, digital twin, geo-BIM, EdgeDisplayMode, CAD edges, model wrong location, model at cente

2026-05-201

package.json

"author": "Impertio-Studio"

"repository": "Impertio-Studio/CesiumJS-Claude-Skill-Package"

فتح مستودع GitHub عرض مستودعات المنشئ

$ install --global

$ download --local

تشغيل في Manus

$ useful --forSOC

مطوّرو البرمجياتمهن الحاسوب والرياضيات15-1252L4

name	cesium-agents-scene-architect
description	Use when starting a new CesiumJS application or feature and deciding how to structure the scene: which viewer class, which imagery and terrain, how to represent a dataset, and whether to enable on-demand rendering. Prevents the wrong-API-tier choice (Entity where 3D Tiles is needed, or the reverse), the continuous-render battery drain, and missing-token blank globes. Orchestrates the CesiumJS skill set into one setup decision path. Keywords: CesiumJS architecture, how do I structure a Cesium app, which viewer, Viewer or CesiumWidget, Entity or Primitive or 3D Tiles, choose imagery provider, choose terrain provider, requestRenderMode, scene setup decision, how do I display my data in Cesium, what API should I use, getting started Cesium scene, plan a Cesium scene.
license	MIT
compatibility	Designed for Claude Code. Requires CesiumJS 1.124+.
metadata	{"author":"OpenAEC-Foundation","version":"1.0"}

Cesium Agents : Scene Architect

Overview

This is an orchestration skill. It does not teach one API; it sequences the setup decisions for a CesiumJS scene and routes each one to the skill that covers it in depth. Follow the decisions in order. Each produces a concrete choice and names the skill to consult.

CesiumJS is WebGL2 only (1.124+). There is no WebGPU path; never plan for one.

When to Use

Starting a new CesiumJS application or a new map feature.
A prompt asks "how should I show this data in Cesium" or "how do I set this up".
Reviewing a scene that was assembled without a clear plan and renders slowly, blank, or wrong.

The Setup Decision Order

Resolve these six decisions in sequence. Skipping ahead causes rework.

digraph setup {
  rankdir=TB; node [shape=box];
  d1 [label="1. Viewer or CesiumWidget"];
  d2 [label="2. Imagery base layer"];
  d3 [label="3. Terrain"];
  d4 [label="4. Data representation per dataset"];
  d5 [label="5. requestRenderMode"];
  d6 [label="6. Teardown plan"];
  d1 -> d2 -> d3 -> d4 -> d5 -> d6;
}

Decision 1 : Viewer or CesiumWidget

digraph viewer {
  q [shape=diamond, label="Need built-in UI widgets\n(timeline, geocoder, infobox)?"];
  v [shape=box, label="Viewer"];
  q2 [shape=diamond, label="Need one or two widgets?"];
  v2 [shape=box, label="Viewer, disable the rest"];
  cw [shape=box, label="CesiumWidget"];
  q -> v [label="yes, most"];
  q -> q2 [label="no / minimal"];
  q2 -> v2 [label="one or two"];
  q2 -> cw [label="none, custom UI"];
}

ALWAYS set Ion.defaultAccessToken before constructing, if any ion asset is used. A missing token is the top cause of a blank globe.
Depth: cesium-core-architecture, cesium-syntax-viewer.

Decision 2 : Imagery Base Layer

Need	Choice	Skill
Cesium-hosted default imagery	`ImageryLayer.fromWorldImagery` (ion)	`cesium-syntax-imagery`
OpenStreetMap raster	`OpenStreetMapImageryProvider`	`cesium-syntax-imagery`
Bing or ArcGIS imagery	`BingMapsImageryProvider`, `ArcGisMapServerImageryProvider`	`cesium-syntax-imagery`
A custom XYZ or WMTS source (incl. MapTiler)	`UrlTemplateImageryProvider` or `WebMapTileServiceImageryProvider`	`cesium-syntax-imagery`
No imagery, abstract globe	construct with `baseLayer: false`	`cesium-syntax-viewer`

All metadata-fetching providers use async factories. NEVER plan around readyPromise.

Decision 3 : Terrain

Need	Choice	Skill
Realistic global elevation	`Terrain.fromWorldTerrain()` or `createWorldTerrainAsync()` (ion)	`cesium-syntax-terrain`
A custom quantized-mesh server	`CesiumTerrainProvider.fromUrl(url)`	`cesium-syntax-terrain`
Esri elevation	`ArcGISTiledElevationTerrainProvider.fromUrl(url)`	`cesium-syntax-terrain`
Flat ellipsoid, no elevation	`EllipsoidTerrainProvider` (default)	`cesium-syntax-terrain`

When terrain is enabled, plan ground clamping for every dataset that must sit on the surface. Depth: cesium-errors-coordinates.

Decision 4 : Data Representation Per Dataset

This is the decision most often made wrong. Choose per dataset.

digraph datarep {
  q1 [shape=diamond, label="Streamed city, point cloud,\nphotogrammetry, or large BIM?"];
  tiles [shape=box, label="3D Tiles : Cesium3DTileset"];
  q2 [shape=diamond, label="Time-dynamic or interactive,\nunder ~10k features?"];
  entity [shape=box, label="Entity API"];
  q3 [shape=diamond, label="Large static geometry set\n(>10k), no time animation?"];
  prim [shape=box, label="Primitive API, batched"];
  single [shape=box, label="One glTF asset: Model.fromGltfAsync"];
  q1 -> tiles [label="yes"];
  q1 -> q2 [label="no"];
  q2 -> entity [label="yes"];
  q2 -> q3 [label="no"];
  q3 -> prim [label="yes"];
  q3 -> single [label="no, a single model"];
}

Representation	Use for	Skill
`Cesium3DTileset`	cities, point clouds, photogrammetry, massive BIM	`cesium-syntax-3d-tiles`, `cesium-impl-3d-tiles-styling`
Entity API	interactive markers, tracks, time-dynamic data under ~10k	`cesium-syntax-entity`, `cesium-syntax-time`
Primitive API	large static geometry sets above ~10k features	`cesium-syntax-primitive`
`Model`	a single glTF or glb asset	`cesium-syntax-gltf-model`
`GeoJsonDataSource`, `KmlDataSource`, `CzmlDataSource`	file-based vector or time-dynamic data	`cesium-syntax-datasources`

NEVER place tens of thousands of individual Entity objects. The per-tick visualizer loop becomes the bottleneck. Use batched primitives or 3D Tiles.
For georeferencing a BIM or CityGML model, see cesium-impl-aec-georef.

Decision 5 : requestRenderMode

digraph rrm {
  q [shape=diamond, label="Does the scene change\nevery frame on its own?"];
  on [shape=box, label="requestRenderMode: true\ncall scene.requestRender() on manual change"];
  off [shape=box, label="Leave continuous rendering"];
  q -> off [label="yes, constant animation"];
  q -> on [label="no, mostly static"];
}

ALWAYS enable requestRenderMode for a static or rarely-changing scene. It is the largest single performance and battery win.
Depth: cesium-core-performance, cesium-core-architecture.

Decision 6 : Teardown Plan

Decide teardown before shipping, not after a leak appears.

ALWAYS plan one viewer.destroy() on the cleanup path.
ALWAYS plan removers for every addEventListener, and destroy() for every ScreenSpaceEventHandler and custom primitive.
In a single-page app or React, plan ONE long-lived viewer, not one per route.
Depth: cesium-core-memory, cesium-errors-memory.

React Applications

When the host app is React, the structural choices above still hold; the component wiring is delegated to cesium-impl-resium.

Output of This Skill

Applying the six decisions yields a written setup plan: the viewer class, the imagery and terrain providers, a representation per dataset, the render mode, and a teardown checklist. Hand each item to the named skill for the code.

Reference Files

references/methods.md : the decision criteria as lookup tables with the governing skill for each.
references/examples.md : three worked scene plans (a static AEC site viewer, a time-dynamic tracking app, a minimal custom-UI globe).
references/anti-patterns.md : the recurring scene-architecture mistakes.

Related Skills

cesium-core-architecture : the object hierarchy these decisions rest on.
cesium-syntax-viewer, cesium-syntax-imagery, cesium-syntax-terrain.
cesium-syntax-entity, cesium-syntax-primitive, cesium-syntax-3d-tiles.
cesium-core-performance, cesium-core-memory.
cesium-agents-skill-validator : checks the generated code after setup.

Sources

Built on the project research base (docs/research/vooronderzoek-cesium.md), itself verified via WebFetch against the CesiumJS API Reference and learn tutorials on the approved sources, 2026-05-20.

cesium-agents-scene-architect

المزيد من هذا المستودع

المزيد من هذا المستودع

Cesium Agents : Scene Architect

Overview

When to Use

The Setup Decision Order

Decision 1 : Viewer or CesiumWidget

Decision 2 : Imagery Base Layer

Decision 3 : Terrain

Decision 4 : Data Representation Per Dataset

Decision 5 : requestRenderMode

Decision 6 : Teardown Plan

React Applications

Output of This Skill

Reference Files

Related Skills

Sources

Cesium Agents : Scene Architect

Overview

When to Use

The Setup Decision Order

Decision 1 : Viewer or CesiumWidget

Decision 2 : Imagery Base Layer

Decision 3 : Terrain

Decision 4 : Data Representation Per Dataset

Decision 5 : requestRenderMode

Decision 6 : Teardown Plan

React Applications

Output of This Skill

Reference Files

Related Skills

Sources