Skip to main contentWhen you can generate tools in minutes instead of building them manually or distracting teammates , you’re free to use them for all sorts of manual and repetitive tasks—from small one-offs to huge, once-painful processes .
- Define what you want the tool to do
- Prompt Bezi with the right details (Steps 1-5, below) and tell it to create a tool
- Bezi will generate a tool to meet your exact purpose and specs!
If you have guidelines or standards that Bezi-generated tools should follow, document them in a Page and pin the page whenever you ask Bezi to create a tool.
The instruction and detail in your prompt dictates the tool’s level of completion and polish…
- Tell Bezi you want it to create a Unity tool
- Define the process or workflow you want to automate
- Define what the tool’s output should be, in as much detail as possible
- Define any tool structure requirements: the form it should take, UI preferences, etc.
- Identify key project references and assets for the tool (assets, pages, scripts, etc.)
- [Agent Mode] Draft a prompt with all the information in Steps 1-5, add anything from Step 5 as in-line pins (type
@, then the name to pin)
- Submit the prompt
- Bezi creates the tool in Unity and writes documentation on how to use it
- Bezi creates all tool scripts in Unity
- If tool set-up requires attaching scripts in-scene, Bezi will give instructions for this step
- Start using your tool!
If you generally like the tool but want to make a few minor edits…
- [Agent Mode] Write another prompt with a detailed explanation of the edits
- Include current state vs desired state
- Attach images for any visual edits
- Submit the prompt and test the updated tool
- Continue to iterate. If any future iterations causes a reversion/problem, edit that prompt to include missing details or specifications
- Select Keep All on the response when you’re happy with the results.
If you want something very different than what was created…
- Click the edit button on the original prompt
- Accept the pop-up to revert changes (this undoes any changes made after the edited prompt)
- Identify what information is missing or needs editing in the original tool prompt to get what you want
- Edit the prompt to account for that missing/incorrect info and submit!
Prompt examples
- Automate a repetitive process/pipeline
- Prompt Example: Make a setup tool that will configure a given animal FBX as a prefab with the necessary components (@AnimalController.cs, Rigidbody, Collider). In the tool UI, include a dropdown for all animal types in @Animals folder, and add the selected animal-type’s script. Follow the rules in @UI-Guidelines-Page.
- Automate UI creation
- Prompt Example: Make a tool that will create the pictured UI for the Achievements screen. Create it as a prefab, use TextMeshPro, and include the ability to assign each sprite. Follow the scaling guidelines in @UI-Guidelines-Page.
- Automate very manual, 1-off setup process
- Prompt Example: Create a partial ragdoll generator tool that I can attach to an object to setup configurable joints on it and all of its children.
- Create a more intuitive interface for a visual/artistic workflow
- Prompt Example: Create a canvas tool to help me lay out and generate new levels. I want to be able to add tiles, with each tile corresponding to a different prefab; place them on the grid; and press a button that generates that layout in-scene.