Project Rules

What are Project Rules?

Project Rules are persistent, reusable context that Bezi applies to every prompt response in a project. Adding Project Rules is the best way to ensure Bezi’s assistance will be consistent with your project’s goals, preferences, and workflows.

Project Rules only apply to the Unity project they’re set in. To apply the same Project Rules across multiple projects, finalize them in one project, then paste them into the other Project Rules pages.

Use Project Rules for:

Output and structural guidelines: define code syntax, input/UI systems, debug strategies, domain-specific knowledge, project-specific workflows, and more
Communication preferences: set Bezi’s tone of voice, your proficiency level, how much instruction you want, and more

How do I access Project Rules?

To access your Project Rules, click the icon in the top left of your app to open the Sidebar. Within the Sidebar, select Project Rules to open the page. Upon opening the Project Rules page, you’ll see some default rules. You can choose to iterate on them or delete them and write your own.

Writing guide and examples

See the Project Rules examples (below) for best practices. Project Rules can be written in natural languange. Like a prompt, an effective Project Rule is focused on a specific purpose. Do not try to pack too much into a single rule. Rules must be: clear, direct, easy to understand, applicable to the entire project Rules should not: contradict each other, be conditional (if…, otherwise…)

Rule examples: Communication preferences

Customize Bezi’s personality and responses

Match Bezi's response style and depth to your experience level

Rule examples: Output and structural guidelines

Set code guidelines and logic

Before you propose code-related changes, review all relevant scripts and analyze their code styles.Make sure all code-related changes you propose, to new or existing scripts, follow the project’s standard coding guidelines:

Use camel case for naming
Prefer long self-explanatory names for variables, methods, and types
Add short summary comments for all methods only and for each step in complex algorithms
Split long code statements into smaller ones
Use constant fields instead of in-place constants
Add logs for better debugging but avoid logs in extensively used methods (like Update)
Avoid combining unrelated responsibilities in a single script. Follow SOLID principles

This is an example of code that follows the project’s standard coding guidelines:

using UnityEngine;

/// <summary> Helps with Raycasting </summary>
public class PhysicsHelper : MonoBehaviour
{
		private LayerMask layerMask = LayerMask.GetMask("Wall", "Character");
	
		// See Order of Execution for Event Functions for information on FixedUpdate() and Update() related to physics queries
		private void FixedUpdate()
		{
			RaycastHit hit;
			// Does the ray intersect any objects excluding the player layer
			// TODO: Remove spammy logs after debugging
			if (Physics.Raycast(transform.position, transform.TransformDirection(Vector3.forward), out hit, Mathf.Infinity, layerMask))
			{
			    Debug.DrawRay(transform.position, transform.TransformDirection(Vector3.forward) * hit.distance, Color.yellow);
					Debug.Log("Did Hit");
			}
			else
			{
					Debug.DrawRay(transform.position, transform.TransformDirection(Vector3.forward) * 1000, Color.white);
					Debug.Log("Did not Hit");
			}
		}
}

Encode system preferences and project-specific knowledge

Explain the game’s concept and goals

Define response steps and workflow requirements

Get Started

Modes

Product

Privacy & Security

Account Settings

Project Rules

What are Project Rules?

How do I access Project Rules?

Writing guide and examples

Rule examples: Communication preferences

Rule examples: Output and structural guidelines

Get Started

Modes

Product

Privacy & Security

Account Settings

​What are Project Rules?

​How do I access Project Rules?

​Writing guide and examples

​Rule examples: Communication preferences

​Rule examples: Output and structural guidelines

What are Project Rules?

How do I access Project Rules?

Writing guide and examples

Rule examples: Communication preferences

Rule examples: Output and structural guidelines