# Vibe coding best practice for cesiumjs

**URL:** <https://community.cesium.com/t/vibe-coding-best-practice-for-cesiumjs/45399>\
**Category:** CesiumJS\
**Created:** [March 4, 2026, 10:57am UTC](https://community.cesium.com/t/vibe-coding-best-practice-for-cesiumjs/45399 "2026-03-04T10:57:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![livizy](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/livizy/32/3476_2.png) [@livizy](https://community.cesium.com/u/livizy)\
**Post date:** [March 4, 2026, 10:57am UTC](https://community.cesium.com/t/vibe-coding-best-practice-for-cesiumjs/45399/1 "2026-03-04T10:57:43Z")

</div>

Is there some vibe coding best practice guidence for cesiumjs use?

---

<div class="post-metadata">

**Author:** ![Ben](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/ben/32/9515_2.png) [@Ben](https://community.cesium.com/u/Ben)\
**Post date:** [March 4, 2026, 10:53pm UTC](https://community.cesium.com/t/vibe-coding-best-practice-for-cesiumjs/45399/2 "2026-03-04T22:53:11Z")

</div>

Hello @livizy,

Welcome back to the forum!

We don’t have any clear guidance written up but I’d be happy to share a few pointers:

- The smaller you go, the better. Asking your AI assistant of choice to build the next greatest CesiumJS app in one prompt will give you plenty of heartache. If you go step by step, function by function, you would see some better results.
- Check out some of our [sandcastles](https://sandcastle.cesium.com/index.html) for inspiration, and feed examples from there into your prompts to follow certain styles.
- Create features in one Index.html file, but ask your AI assistant of choice what a good architectural structure would be for your web application. Are components easy to add and remove? Is it scalable?

Following these steps should get you off on the right foot. We are very interested in making agentic workflows more accessible to users like yourself, so keep a look out!

---

<div class="post-metadata">

**Author:** ![livizy](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/livizy/32/3476_2.png) [@livizy](https://community.cesium.com/u/livizy)\
**Post date:** [March 5, 2026, 12:55am UTC](https://community.cesium.com/t/vibe-coding-best-practice-for-cesiumjs/45399/3 "2026-03-05T00:55:33Z")

</div>

What I actually mean is whether there can be an official AI integration approach for Cesium’s online documentation or Sandcastles, just like what LangChain has done at [https://docs.langchain.com/mcp](https://docs.langchain.com/mcp).

---

<div class="post-metadata">

**Author:** ![livizy](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/livizy/32/3476_2.png) [@livizy](https://community.cesium.com/u/livizy)\
**Post date:** [March 5, 2026, 12:56am UTC](https://community.cesium.com/t/vibe-coding-best-practice-for-cesiumjs/45399/4 "2026-03-05T00:56:25Z")

</div>

And，I found content out of time about cesium in skills.sh  
[creating-globe-tours by cesiumgs/cesium-ai-integrations](https://skills.sh/cesiumgs/cesium-ai-integrations/creating-globe-tours)

---

<div class="post-metadata">

**Author:** ![Margarita.Kart](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/margarita.kart/32/28173_2.png) [@Margarita.Kart](https://community.cesium.com/u/Margarita.Kart)\
**Post date:** [March 6, 2026, 11:48am UTC](https://community.cesium.com/t/vibe-coding-best-practice-for-cesiumjs/45399/5 "2026-03-06T11:48:11Z")

</div>

Hello @livizy,

We’ve recently launched a new repository for **Cesium + AI integrations** :  
[GitHub - CesiumGS/cesium-ai-integrations · GitHub](https://github.com/CesiumGS/cesium-ai-integrations/tree/main) .  
Our goal is to provide examples and resources that help developers use Cesium effectively with AI.

To reduce hallucinations when working with Cesium APIs, we’ve also created a guide on how to use the **Context7 MCP server** to fetch official Cesium documentation:

> <https://github.com/CesiumGS/cesium-ai-integrations/blob/main/mcp/external/cesium-context7/README.md>

Additionally, we’ve published a **skill** that helps AI assistants interact with the Context7 MCP server:

> <https://github.com/CesiumGS/cesium-ai-integrations/blob/main/skills/cesium-context7/SKILL.md>

We invite you to try it out and see whether it meets your needs.  
If you have feedback about using Context7 MCP to consume Cesium documentation, please share it here:

> [@Fight AI Hallucination in Cesium Development — Your Feedback Is Needed!](https://community.cesium.com/t/fight-ai-hallucination-in-cesium-development-your-feedback-is-needed/44979):
>
> Hi Cesium Community, We’re currently exploring ways to enhance the development experience with Cesium by integrating AI assistants into the workflow. As part of this effort, we’ve been experimenting with Context7 ( [Context7 - Up-to-date documentation for LLMs and AI code editors](https://context7.com/?q=cesium) ), an MCP (Model Context Protocol) server that provides AI tools with real‑time access to the latest documentation, source code references, and API details. At the moment, Context7 has five Cesium‑related documentatio…

Are there any specific skills or tooling you’d be interested in seeing added to the Cesium + AI integrations project?

---

<div class="post-metadata">

**Author:** ![livizy](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/livizy/32/3476_2.png) [@livizy](https://community.cesium.com/u/livizy)\
**Post date:** [March 6, 2026, 1:15pm UTC](https://community.cesium.com/t/vibe-coding-best-practice-for-cesiumjs/45399/6 "2026-03-06T13:15:54Z")

</div>

![image](https://global.discourse-cdn.com/cesium/original/3X/7/5/75e5e1b2be0fa8132df478d82f2630a9b4e910ce.png)  
has been scaned by skills.sh 😆
