Project Instructions

Use AGENTS.md files to give Atlas reusable project conventions. Instructions apply to asking, planning, generation, modification, correction, testing, and review, according to the relevant project or file scope.

Add project conventions

Create AGENTS.md at the Unity project root, beside Assets, Packages, and ProjectSettings. Keep it concise and actionable:

Use the Studio.Gameplay namespace for our runtime scripts.
Use serialized private fields for inspector references.
Prefer existing project components over a second implementation.
Do not rename existing serialized fields without explaining migration.
For gameplay changes, describe missing-reference and interruption tests.

Do not put credentials, tokens, or other secrets in this file. Applicable instruction contents are sent with the request.

Folder-specific instructions

Add another AGENTS.md inside a narrower folder, such as Assets/AI/Tasks, to define rules for that subtree. Atlas reads applicable files from the project root down to the relevant destination or source folder. Deeper files refine conflicting ancestor rules for their own scope.

Generation and planning use the current save folder. Modify, review, tests, and correction use their actual source or saved-file paths. General questions use the project root.

If you save a result into a folder with a different instruction chain, Atlas warns before writing so you can regenerate for the new destination.

Choose an alternative base file

Open Settings > Project instructions > Choose AGENTS.md… to select a project-wide base instruction file inside the Unity project. Automatically discovered nested files continue to refine it.

Choose Clear chosen file to return to discovery-only behavior. Use project AGENTS.md enables or disables instruction collection; it is enabled by default.

Precedence and limits

Project instructions cannot override Atlas’s product rules, response format, or source validation. Within those boundaries, project instructions take precedence over conflicting task-specific preferences, and deeper instruction files take precedence over ancestors.

Atlas accepts up to 16 instruction documents, 32 KB per document, and 64 KB in total. Empty or oversized documents, linked files or directories, and paths outside the project are ignored with a Unity warning.

Natural-language conventions are model guidance, not a guarantee enforced by a compiler. Inspect the result for compliance and keep deterministic formatting or analysis checks in your normal development workflow.

See Privacy and project data and Generating and applying code.