Skip to main content
Bezi understands the contents of a project, the objects in a scene, and the properties on the assets, so it’s well-equipped to parse through it all and deliver the exact information you need. Ask Bezi to navigate the depths of your project to find the little details that take endless time to recover. And breathe easy knowing project documentation is covered, without spending time on it.
Currently, Bezi’s context does not dive into node graphs, state machines, or visual scripting. Bezi is aware they exist, but cannot see or explain how objects like animators and shader graphs are set up.
To use Bezi to track and document how a feature, system or project evolves over time, follow these steps:
  1. Prompt Bezi to write detailed documentation for the scope in question
  2. Copy and paste the in-thread documentation into a Page
  3. Title the Page according to the scope and date
  4. Ask Bezi to generate documentation on how the current version is different from the original, tagging the Page you created so Bezi knows to use it as the “origional” datapoint
    1. “Write me detailed documentation on the current version of @[scope] and how it is different from the origional @[Page-name]”
  5. Voila! Bezi’s written your detailed documentation and changelog

​
Example prompts

Onboarding:
  • “Tell me about this project”
  • “Walk me through @PlayerInteraction.cs”
  • “Explain the key features of the PortalsForVR package.”
  • “How does the multiplayer system in this game work?””
  • “What are the controls for this game? List what mechanics there are, and explain how to use each to test.”
Property/Type:
  • “Find all objects set to Static”
  • “Which colliders are set to isTrigger?”
  • “Do I have multiple cameras tagged MainCam?”
  • “List all food prefabs”
Dependencies:
  • “What tile palettes were used to build this level?”
  • “Return all scripts that instantiate Prey prefabs”
  • “Which animation clips does my character movement system actually use?”
  • “What script controls the pickup/drop behavior?”
Optimization:
  • “List all 4K textures”
  • “What models do I actually use across my scenes?”
  • “Which models are too high poly to run on mobile?”
⌘I