Is there some vibe coding best practice guidence for cesiumjs use?
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 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!
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.
And，I found content out of time about cesium in skills.sh
creating-globe-tours by cesiumgs/cesium-ai-integrations
Hello @livizy,
We’ve recently launched a new repository for Cesium + AI integrations:
GitHub - CesiumGS/cesium-ai-integrations · GitHub .
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:
Additionally, we’ve published a skill that helps AI assistants interact with the Context7 MCP server:
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:
Are there any specific skills or tooling you’d be interested in seeing added to the Cesium + AI integrations project?
