Skip to main content
Bezi understands the structure of a project and its contents - down to the smallest detail. So it’s well-equipped to deliver the exact information you need!

​
Prompt examples

  1. Get onboarded to a new or unfamilar project
    • Prompt Example: “Tell me about this project”
    • Prompt Example: “How does the multiplayer system in this game work?”
    • Prompt Example: “What are the controls for this game? List what mechanics there are, and explain how to use each to test.”
  2. Identify all relevant properties / types
    • Prompt Example: “Find all objects set to Static”
    • Prompt Example: “Do I have multiple cameras tagged MainCam?”
    • Prompt Example: “List all food prefabs”
  3. Quickly find all dependencies
    • Prompt Example: “What tile palettes were used to build this level?”
    • Prompt Example: “Return all scripts that instantiate Prey prefabs”
    • Prompt Example: “Which animation clips does my character movement system actually use?”
    • Prompt Example: “What script controls the pickup/drop behavior?”
  4. Find low-hanging fruit for optimization
    • Prompt Example: “List all 4K textures”
    • Prompt Example: “What models do I actually use across my scenes?”
    • Prompt Example: “Which models are too high poly to run on mobile?”

​
Document how a part of the project changes over time:

  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, pinning 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