A few rules before more automation
Where files belong, what is already there, and which changes are ready to share.
When coding agents work across several projects, a few ordinary decisions matter: where to put files, which branch to use, and what is ready to share.
Project Rules is where I keep a common starting point for those decisions.
Check what is already there
Before changing a repository, inspect its branch and uncommitted work. Existing edits may belong to another task. A new change should not overwrite them or quietly include them in a commit.
Give the work a home
Personal projects, experiments and finished outputs do not all need the same destination. Decide where a piece of work belongs before creating more files.
Keep publishing explicit
A local edit, a GitHub push and a deployment are different steps. The workflow should make clear which step is authorized and what is still waiting for review.
The point is not more paperwork. It is less guessing, fewer mixed-up changes, and work that is easier to return to later.