Context7 for Cesium Development
This skill provides access to up-to-date Cesium documentation for CesiumJS, Unreal Engine integration, and Unity integration.
When working with Cesium-related code, use Context7 MCP Server tools to fetch current documentation before providing answers or generating code.
Available Tools
1. resolve-library-id
Search for libraries and retrieve their Context7 library IDs.
⚠️ Only use this tool when it's unclear which library to use. For Cesium projects, use the Known Library IDs listed below.
Parameters:
libraryName (string, required): Name of the library to searchquery (string, optional): Additional search context
Example use case: Find the correct library ID for an unfamiliar library or when the library ID is unknown.
2. query-docs
Retrieve documentation for a specific library and query.
Parameters:
libraryId (string, required): Context7 library IDquery (string, required): Documentation query or topicversion (string, optional): Specific library version
Example use case: Get documentation for Cesium Viewer initialization using library /cesiumgs/cesium.
Known Library IDs
CesiumJS API Documentation
For class constructors, methods, and properties (e.g., Viewer, Entity, Cartesian3, Camera methods, Scene properties):
- Library ID:
/cesiumgs/cesium
Cesium for Unreal Engine
For Unreal Engine integration (e.g., ACesium3DTileset, ACesiumGeoreference, Blueprint integration):
- Library ID:
/cesiumgs/cesium-unreal
Cesium for Unity
For Unity integration (e.g., Cesium3DTileset component, CesiumCameraController, C# scripting):
- Library ID:
/cesiumgs/cesium-unity
3D Tiles Specification
For tile formats and schema details (e.g., tileset JSON structure, refinement strategies, metadata schemas):
- Library ID:
/websites/ogc_cs_22-025r4
Usage Guidelines
- Use the Known Library IDs listed above for Cesium-related queries
- When a question requires information from multiple sources (e.g., CesiumJS API + 3D Tiles spec, or Unreal integration + CesiumJS concepts), make separate
query-docs calls with different library IDs to gather comprehensive documentation
- Use
resolve-library-id when the library is unknown, not listed in Known Library IDs, or when it's unclear which library best fits the question
- Use
query-docs to fetch documentation before generating code to ensure accuracy
- Specify the
version parameter when working with a specific version
- Provide clear, specific queries to get the most relevant documentation
- Avoid hallucinations by using current, version-specific documentation
1---2name: cesium-context73description: Fetches up-to-date documentation for Cesium, CesiumJS, Cesium Viewer, 3D Tiles, Unreal Engine integration, Unity integration, cesium-unreal, cesium-unity, ACesium3DTileset, ACesiumGeoreference, Globe Anchor, Cesium plugin, georeferencing, and Cesium-related APIs using Context7 MCP tools. Useful for CesiumJS classes (Viewer, Entity, Camera, Scene, Cartesian3, etc.), Unreal Engine Cesium components, Unity Cesium components, 3D Tiles specification, and Cesium integrations. Use query-docs with library IDs: /cesiumgs/cesium (CesiumJS), /cesiumgs/cesium-unreal (Unreal), /cesiumgs/cesium-unity (Unity), /websites/ogc_cs_22-025r4 (3D Tiles spec).4---5
6# Context7 for Cesium Development
7
8This skill provides access to up-to-date Cesium documentation for CesiumJS, Unreal Engine integration, and Unity integration.
9
10When working with Cesium-related code, use Context7 MCP Server tools to fetch current documentation before providing answers or generating code.
11
12## Available Tools
13
14### 1. `resolve-library-id`
15
16Search for libraries and retrieve their Context7 library IDs.
17
18**⚠️ Only use this tool when it's unclear which library to use. For Cesium projects, use the Known Library IDs listed below.**
19
20**Parameters**:
21
22- `libraryName` (string, required): Name of the library to search
23- `query` (string, optional): Additional search context
24
25**Example use case**: Find the correct library ID for an unfamiliar library or when the library ID is unknown.
26
27### 2. `query-docs`
28
29Retrieve documentation for a specific library and query.
30
31**Parameters**:
32
33- `libraryId` (string, required): Context7 library ID
34- `query` (string, required): Documentation query or topic
35- `version` (string, optional): Specific library version
36
37**Example use case**: Get documentation for Cesium Viewer initialization using library `/cesiumgs/cesium`.
38
39## Known Library IDs
40
41### CesiumJS API Documentation
42
43For class constructors, methods, and properties (e.g., Viewer, Entity, Cartesian3, Camera methods, Scene properties):
44
45- Library ID: `/cesiumgs/cesium`
46
47### Cesium for Unreal Engine
48
49For Unreal Engine integration (e.g., ACesium3DTileset, ACesiumGeoreference, Blueprint integration):
50
51- Library ID: `/cesiumgs/cesium-unreal`
52
53### Cesium for Unity
54
55For Unity integration (e.g., Cesium3DTileset component, CesiumCameraController, C# scripting):
56
57- Library ID: `/cesiumgs/cesium-unity`
58
59### 3D Tiles Specification
60
61For tile formats and schema details (e.g., tileset JSON structure, refinement strategies, metadata schemas):
62
63- Library ID: `/websites/ogc_cs_22-025r4`
64
65## Usage Guidelines
66
67- Use the Known Library IDs listed above for Cesium-related queries
68- When a question requires information from multiple sources (e.g., CesiumJS API + 3D Tiles spec, or Unreal integration + CesiumJS concepts), make separate `query-docs` calls with different library IDs to gather comprehensive documentation
69- Use `resolve-library-id` when the library is unknown, not listed in Known Library IDs, or when it's unclear which library best fits the question
70- Use `query-docs` to fetch documentation before generating code to ensure accuracy
71- Specify the `version` parameter when working with a specific version
72- Provide clear, specific queries to get the most relevant documentation
73- Avoid hallucinations by using current, version-specific documentation
majiayu000