Godot 4 rules file

---description: "Project rules for GDScript, Godot, GUT, Godot project. Generated by RulePaste."alwaysApply: true--- # Project rules Stack: GDScript, Godot, GUT, Godot project. Follow these rules on every task. If a rule disagrees with existing code, match the code and mention the difference. If a rule disagrees with a direct user instruction, follow the user. ## Working agreement - Read the files you will change before editing them. Do not invent the project layout from memory.- Change only what the task needs. No drive-by refactors, renames, or formatting of untouched lines.- Match the patterns already in the repo over a generic style guide.- Do not add dependencies, config files, or abstractions the task did not ask for.- Do not commit secrets, and do not paste `.env` values, tokens, or private keys into code or chat.- If a requirement is ambiguous, choose the smallest reading, state that assumption, and continue. ## Commands - This is a Godot 4 project. Do not add a Node or Python toolchain unless a subfolder already has one.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files.- Run GUT only if `addons/gut` is installed. Use the headless command the repo already documents. ## GDScript - Type variables, parameters, and return values.- `snake_case` for functions, variables, and signals. `PascalCase` for classes and node names. Signal names are past tense, such as `health_changed`.- Cache node references with `@onready` and unique names. Do not call `get_node` every frame.- Keep the file's indentation. Godot's default is tabs. Do not convert a file to spaces. ## Godot - Use the Godot feature tag already in `project.godot`. Do not change it as a side effect.- A script assumes only the nodes in its own scene. Call down to children and signal up to parents.- Do not reach across the tree with absolute node paths. Do not add an autoload for one scene's state.- Use `_physics_process` for movement and `_process` otherwise. Multiply speeds by `delta`.- Do not edit the `.godot/` cache. Commit `project.godot`, scenes, scripts, and `.import` files.- Prefer containers and anchors for UI that must resize. Do not hard-code a full-screen layout in pixels. ## GUT - If the GUT addon is installed, extend `GutTest` and use `assert_eq` and `assert_true`. Do not print and eyeball.- Instance any scene the test needs inside the test. Do not require the editor to be open.- Do not add a second Godot test framework beside GUT. ## Godot project files - Do not introduce Node, Python, or another toolchain unless a subfolder already has it.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files. ## Testing expectations - When you fix a bug, add a test that fails before the fix and passes after, in the repo's current test style.- When you change behavior a caller can observe, update or add a test for that behavior.- Do not test private helpers, framework internals, or third-party libraries. ## Code style - Keep strict type and lint settings on. Do not weaken them to get a green build.- No new `any`, and no empty catch blocks. Prefer `unknown` and narrowing. Handle every fallible call.- Give exported functions an explicit type when the inferred type is not obvious.- Follow the repo formatter. Do not hand-format files the formatter owns.- Do not add comments that restate the code.- Comment only a constraint, invariant, or tradeoff the code itself cannot show.- No file-header banners and no changelog comments. ## Safety - Never commit `.env`, keystores, or credential files. When a new variable is required, add an empty placeholder to the example env file.- Do not disable authentication, authorization, or TLS checks to make a test pass.- Do not force-push, `reset --hard`, drop a database, or delete a directory tree unless the user asked for that exact action.- Do not edit vendored or generated output (`node_modules`, `dist`, `.next`, `vendor`, `Library`, `.godot`). Change the source and regenerate. ## Done when - The change does what was asked and nothing extra.- New or changed behavior is covered at the level in Testing expectations.- The commands in this file that apply to the touched files have been run, or you say which command you could not run.- The diff has no unrelated files, lockfile churn, or secrets. 

# Project rules Stack: GDScript, Godot, GUT, Godot project. Follow these rules on every task. If a rule disagrees with existing code, match the code and mention the difference. If a rule disagrees with a direct user instruction, follow the user. ## Working agreement - Read the files you will change before editing them. Do not invent the project layout from memory.- Change only what the task needs. No drive-by refactors, renames, or formatting of untouched lines.- Match the patterns already in the repo over a generic style guide.- Do not add dependencies, config files, or abstractions the task did not ask for.- Do not commit secrets, and do not paste `.env` values, tokens, or private keys into code or chat.- If a requirement is ambiguous, choose the smallest reading, state that assumption, and continue. ## Commands - This is a Godot 4 project. Do not add a Node or Python toolchain unless a subfolder already has one.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files.- Run GUT only if `addons/gut` is installed. Use the headless command the repo already documents. ## GDScript - Type variables, parameters, and return values.- `snake_case` for functions, variables, and signals. `PascalCase` for classes and node names. Signal names are past tense, such as `health_changed`.- Cache node references with `@onready` and unique names. Do not call `get_node` every frame.- Keep the file's indentation. Godot's default is tabs. Do not convert a file to spaces. ## Godot - Use the Godot feature tag already in `project.godot`. Do not change it as a side effect.- A script assumes only the nodes in its own scene. Call down to children and signal up to parents.- Do not reach across the tree with absolute node paths. Do not add an autoload for one scene's state.- Use `_physics_process` for movement and `_process` otherwise. Multiply speeds by `delta`.- Do not edit the `.godot/` cache. Commit `project.godot`, scenes, scripts, and `.import` files.- Prefer containers and anchors for UI that must resize. Do not hard-code a full-screen layout in pixels. ## GUT - If the GUT addon is installed, extend `GutTest` and use `assert_eq` and `assert_true`. Do not print and eyeball.- Instance any scene the test needs inside the test. Do not require the editor to be open.- Do not add a second Godot test framework beside GUT. ## Godot project files - Do not introduce Node, Python, or another toolchain unless a subfolder already has it.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files. ## Testing expectations - When you fix a bug, add a test that fails before the fix and passes after, in the repo's current test style.- When you change behavior a caller can observe, update or add a test for that behavior.- Do not test private helpers, framework internals, or third-party libraries. ## Code style - Keep strict type and lint settings on. Do not weaken them to get a green build.- No new `any`, and no empty catch blocks. Prefer `unknown` and narrowing. Handle every fallible call.- Give exported functions an explicit type when the inferred type is not obvious.- Follow the repo formatter. Do not hand-format files the formatter owns.- Do not add comments that restate the code.- Comment only a constraint, invariant, or tradeoff the code itself cannot show.- No file-header banners and no changelog comments. ## Safety - Never commit `.env`, keystores, or credential files. When a new variable is required, add an empty placeholder to the example env file.- Do not disable authentication, authorization, or TLS checks to make a test pass.- Do not force-push, `reset --hard`, drop a database, or delete a directory tree unless the user asked for that exact action.- Do not edit vendored or generated output (`node_modules`, `dist`, `.next`, `vendor`, `Library`, `.godot`). Change the source and regenerate. ## Done when - The change does what was asked and nothing extra.- New or changed behavior is covered at the level in Testing expectations.- The commands in this file that apply to the touched files have been run, or you say which command you could not run.- The diff has no unrelated files, lockfile churn, or secrets. 

# Project rules Stack: GDScript, Godot, GUT, Godot project. Follow these rules on every task. If a rule disagrees with existing code, match the code and mention the difference. If a rule disagrees with a direct user instruction, follow the user. ## Working agreement - Read the files you will change before editing them. Do not invent the project layout from memory.- Change only what the task needs. No drive-by refactors, renames, or formatting of untouched lines.- Match the patterns already in the repo over a generic style guide.- Do not add dependencies, config files, or abstractions the task did not ask for.- Do not commit secrets, and do not paste `.env` values, tokens, or private keys into code or chat.- If a requirement is ambiguous, choose the smallest reading, state that assumption, and continue. ## Commands - This is a Godot 4 project. Do not add a Node or Python toolchain unless a subfolder already has one.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files.- Run GUT only if `addons/gut` is installed. Use the headless command the repo already documents. ## GDScript - Type variables, parameters, and return values.- `snake_case` for functions, variables, and signals. `PascalCase` for classes and node names. Signal names are past tense, such as `health_changed`.- Cache node references with `@onready` and unique names. Do not call `get_node` every frame.- Keep the file's indentation. Godot's default is tabs. Do not convert a file to spaces. ## Godot - Use the Godot feature tag already in `project.godot`. Do not change it as a side effect.- A script assumes only the nodes in its own scene. Call down to children and signal up to parents.- Do not reach across the tree with absolute node paths. Do not add an autoload for one scene's state.- Use `_physics_process` for movement and `_process` otherwise. Multiply speeds by `delta`.- Do not edit the `.godot/` cache. Commit `project.godot`, scenes, scripts, and `.import` files.- Prefer containers and anchors for UI that must resize. Do not hard-code a full-screen layout in pixels. ## GUT - If the GUT addon is installed, extend `GutTest` and use `assert_eq` and `assert_true`. Do not print and eyeball.- Instance any scene the test needs inside the test. Do not require the editor to be open.- Do not add a second Godot test framework beside GUT. ## Godot project files - Do not introduce Node, Python, or another toolchain unless a subfolder already has it.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files. ## Testing expectations - When you fix a bug, add a test that fails before the fix and passes after, in the repo's current test style.- When you change behavior a caller can observe, update or add a test for that behavior.- Do not test private helpers, framework internals, or third-party libraries. ## Code style - Keep strict type and lint settings on. Do not weaken them to get a green build.- No new `any`, and no empty catch blocks. Prefer `unknown` and narrowing. Handle every fallible call.- Give exported functions an explicit type when the inferred type is not obvious.- Follow the repo formatter. Do not hand-format files the formatter owns.- Do not add comments that restate the code.- Comment only a constraint, invariant, or tradeoff the code itself cannot show.- No file-header banners and no changelog comments. ## Safety - Never commit `.env`, keystores, or credential files. When a new variable is required, add an empty placeholder to the example env file.- Do not disable authentication, authorization, or TLS checks to make a test pass.- Do not force-push, `reset --hard`, drop a database, or delete a directory tree unless the user asked for that exact action.- Do not edit vendored or generated output (`node_modules`, `dist`, `.next`, `vendor`, `Library`, `.godot`). Change the source and regenerate. ## Done when - The change does what was asked and nothing extra.- New or changed behavior is covered at the level in Testing expectations.- The commands in this file that apply to the touched files have been run, or you say which command you could not run.- The diff has no unrelated files, lockfile churn, or secrets. 

---trigger: always_ondescription: "Project rules for GDScript, Godot, GUT, Godot project. Generated by RulePaste."--- # Project rules Stack: GDScript, Godot, GUT, Godot project. Follow these rules on every task. If a rule disagrees with existing code, match the code and mention the difference. If a rule disagrees with a direct user instruction, follow the user. ## Working agreement - Read the files you will change before editing them. Do not invent the project layout from memory.- Change only what the task needs. No drive-by refactors, renames, or formatting of untouched lines.- Match the patterns already in the repo over a generic style guide.- Do not add dependencies, config files, or abstractions the task did not ask for.- Do not commit secrets, and do not paste `.env` values, tokens, or private keys into code or chat.- If a requirement is ambiguous, choose the smallest reading, state that assumption, and continue. ## Commands - This is a Godot 4 project. Do not add a Node or Python toolchain unless a subfolder already has one.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files.- Run GUT only if `addons/gut` is installed. Use the headless command the repo already documents. ## GDScript - Type variables, parameters, and return values.- `snake_case` for functions, variables, and signals. `PascalCase` for classes and node names. Signal names are past tense, such as `health_changed`.- Cache node references with `@onready` and unique names. Do not call `get_node` every frame.- Keep the file's indentation. Godot's default is tabs. Do not convert a file to spaces. ## Godot - Use the Godot feature tag already in `project.godot`. Do not change it as a side effect.- A script assumes only the nodes in its own scene. Call down to children and signal up to parents.- Do not reach across the tree with absolute node paths. Do not add an autoload for one scene's state.- Use `_physics_process` for movement and `_process` otherwise. Multiply speeds by `delta`.- Do not edit the `.godot/` cache. Commit `project.godot`, scenes, scripts, and `.import` files.- Prefer containers and anchors for UI that must resize. Do not hard-code a full-screen layout in pixels. ## GUT - If the GUT addon is installed, extend `GutTest` and use `assert_eq` and `assert_true`. Do not print and eyeball.- Instance any scene the test needs inside the test. Do not require the editor to be open.- Do not add a second Godot test framework beside GUT. ## Godot project files - Do not introduce Node, Python, or another toolchain unless a subfolder already has it.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files. ## Testing expectations - When you fix a bug, add a test that fails before the fix and passes after, in the repo's current test style.- When you change behavior a caller can observe, update or add a test for that behavior.- Do not test private helpers, framework internals, or third-party libraries. ## Code style - Keep strict type and lint settings on. Do not weaken them to get a green build.- No new `any`, and no empty catch blocks. Prefer `unknown` and narrowing. Handle every fallible call.- Give exported functions an explicit type when the inferred type is not obvious.- Follow the repo formatter. Do not hand-format files the formatter owns.- Do not add comments that restate the code.- Comment only a constraint, invariant, or tradeoff the code itself cannot show.- No file-header banners and no changelog comments. ## Safety - Never commit `.env`, keystores, or credential files. When a new variable is required, add an empty placeholder to the example env file.- Do not disable authentication, authorization, or TLS checks to make a test pass.- Do not force-push, `reset --hard`, drop a database, or delete a directory tree unless the user asked for that exact action.- Do not edit vendored or generated output (`node_modules`, `dist`, `.next`, `vendor`, `Library`, `.godot`). Change the source and regenerate. ## Done when - The change does what was asked and nothing extra.- New or changed behavior is covered at the level in Testing expectations.- The commands in this file that apply to the touched files have been run, or you say which command you could not run.- The diff has no unrelated files, lockfile churn, or secrets. 

# Project rules Stack: GDScript, Godot, GUT, Godot project. Follow these rules on every task. If a rule disagrees with existing code, match the code and mention the difference. If a rule disagrees with a direct user instruction, follow the user. ## Working agreement - Read the files you will change before editing them. Do not invent the project layout from memory.- Change only what the task needs. No drive-by refactors, renames, or formatting of untouched lines.- Match the patterns already in the repo over a generic style guide.- Do not add dependencies, config files, or abstractions the task did not ask for.- Do not commit secrets, and do not paste `.env` values, tokens, or private keys into code or chat.- If a requirement is ambiguous, choose the smallest reading, state that assumption, and continue. ## Commands - This is a Godot 4 project. Do not add a Node or Python toolchain unless a subfolder already has one.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files.- Run GUT only if `addons/gut` is installed. Use the headless command the repo already documents. ## GDScript - Type variables, parameters, and return values.- `snake_case` for functions, variables, and signals. `PascalCase` for classes and node names. Signal names are past tense, such as `health_changed`.- Cache node references with `@onready` and unique names. Do not call `get_node` every frame.- Keep the file's indentation. Godot's default is tabs. Do not convert a file to spaces. ## Godot - Use the Godot feature tag already in `project.godot`. Do not change it as a side effect.- A script assumes only the nodes in its own scene. Call down to children and signal up to parents.- Do not reach across the tree with absolute node paths. Do not add an autoload for one scene's state.- Use `_physics_process` for movement and `_process` otherwise. Multiply speeds by `delta`.- Do not edit the `.godot/` cache. Commit `project.godot`, scenes, scripts, and `.import` files.- Prefer containers and anchors for UI that must resize. Do not hard-code a full-screen layout in pixels. ## GUT - If the GUT addon is installed, extend `GutTest` and use `assert_eq` and `assert_true`. Do not print and eyeball.- Instance any scene the test needs inside the test. Do not require the editor to be open.- Do not add a second Godot test framework beside GUT. ## Godot project files - Do not introduce Node, Python, or another toolchain unless a subfolder already has it.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files. ## Testing expectations - When you fix a bug, add a test that fails before the fix and passes after, in the repo's current test style.- When you change behavior a caller can observe, update or add a test for that behavior.- Do not test private helpers, framework internals, or third-party libraries. ## Code style - Keep strict type and lint settings on. Do not weaken them to get a green build.- No new `any`, and no empty catch blocks. Prefer `unknown` and narrowing. Handle every fallible call.- Give exported functions an explicit type when the inferred type is not obvious.- Follow the repo formatter. Do not hand-format files the formatter owns.- Do not add comments that restate the code.- Comment only a constraint, invariant, or tradeoff the code itself cannot show.- No file-header banners and no changelog comments. ## Safety - Never commit `.env`, keystores, or credential files. When a new variable is required, add an empty placeholder to the example env file.- Do not disable authentication, authorization, or TLS checks to make a test pass.- Do not force-push, `reset --hard`, drop a database, or delete a directory tree unless the user asked for that exact action.- Do not edit vendored or generated output (`node_modules`, `dist`, `.next`, `vendor`, `Library`, `.godot`). Change the source and regenerate. ## Done when - The change does what was asked and nothing extra.- New or changed behavior is covered at the level in Testing expectations.- The commands in this file that apply to the touched files have been run, or you say which command you could not run.- The diff has no unrelated files, lockfile churn, or secrets. 

# Project rules Stack: GDScript, Godot, GUT, Godot project. Follow these rules on every task. If a rule disagrees with existing code, match the code and mention the difference. If a rule disagrees with a direct user instruction, follow the user. ## Working agreement - Read the files you will change before editing them. Do not invent the project layout from memory.- Change only what the task needs. No drive-by refactors, renames, or formatting of untouched lines.- Match the patterns already in the repo over a generic style guide.- Do not add dependencies, config files, or abstractions the task did not ask for.- Do not commit secrets, and do not paste `.env` values, tokens, or private keys into code or chat.- If a requirement is ambiguous, choose the smallest reading, state that assumption, and continue. ## Commands - This is a Godot 4 project. Do not add a Node or Python toolchain unless a subfolder already has one.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files.- Run GUT only if `addons/gut` is installed. Use the headless command the repo already documents. ## GDScript - Type variables, parameters, and return values.- `snake_case` for functions, variables, and signals. `PascalCase` for classes and node names. Signal names are past tense, such as `health_changed`.- Cache node references with `@onready` and unique names. Do not call `get_node` every frame.- Keep the file's indentation. Godot's default is tabs. Do not convert a file to spaces. ## Godot - Use the Godot feature tag already in `project.godot`. Do not change it as a side effect.- A script assumes only the nodes in its own scene. Call down to children and signal up to parents.- Do not reach across the tree with absolute node paths. Do not add an autoload for one scene's state.- Use `_physics_process` for movement and `_process` otherwise. Multiply speeds by `delta`.- Do not edit the `.godot/` cache. Commit `project.godot`, scenes, scripts, and `.import` files.- Prefer containers and anchors for UI that must resize. Do not hard-code a full-screen layout in pixels. ## GUT - If the GUT addon is installed, extend `GutTest` and use `assert_eq` and `assert_true`. Do not print and eyeball.- Instance any scene the test needs inside the test. Do not require the editor to be open.- Do not add a second Godot test framework beside GUT. ## Godot project files - Do not introduce Node, Python, or another toolchain unless a subfolder already has it.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files. ## Testing expectations - When you fix a bug, add a test that fails before the fix and passes after, in the repo's current test style.- When you change behavior a caller can observe, update or add a test for that behavior.- Do not test private helpers, framework internals, or third-party libraries. ## Code style - Keep strict type and lint settings on. Do not weaken them to get a green build.- No new `any`, and no empty catch blocks. Prefer `unknown` and narrowing. Handle every fallible call.- Give exported functions an explicit type when the inferred type is not obvious.- Follow the repo formatter. Do not hand-format files the formatter owns.- Do not add comments that restate the code.- Comment only a constraint, invariant, or tradeoff the code itself cannot show.- No file-header banners and no changelog comments. ## Safety - Never commit `.env`, keystores, or credential files. When a new variable is required, add an empty placeholder to the example env file.- Do not disable authentication, authorization, or TLS checks to make a test pass.- Do not force-push, `reset --hard`, drop a database, or delete a directory tree unless the user asked for that exact action.- Do not edit vendored or generated output (`node_modules`, `dist`, `.next`, `vendor`, `Library`, `.godot`). Change the source and regenerate. ## Done when - The change does what was asked and nothing extra.- New or changed behavior is covered at the level in Testing expectations.- The commands in this file that apply to the touched files have been run, or you say which command you could not run.- The diff has no unrelated files, lockfile churn, or secrets. 

# Project rules Stack: GDScript, Godot, GUT, Godot project. Follow these rules on every task. If a rule disagrees with existing code, match the code and mention the difference. If a rule disagrees with a direct user instruction, follow the user. ## Working agreement - Read the files you will change before editing them. Do not invent the project layout from memory.- Change only what the task needs. No drive-by refactors, renames, or formatting of untouched lines.- Match the patterns already in the repo over a generic style guide.- Do not add dependencies, config files, or abstractions the task did not ask for.- Do not commit secrets, and do not paste `.env` values, tokens, or private keys into code or chat.- If a requirement is ambiguous, choose the smallest reading, state that assumption, and continue. ## Commands - This is a Godot 4 project. Do not add a Node or Python toolchain unless a subfolder already has one.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files.- Run GUT only if `addons/gut` is installed. Use the headless command the repo already documents. ## GDScript - Type variables, parameters, and return values.- `snake_case` for functions, variables, and signals. `PascalCase` for classes and node names. Signal names are past tense, such as `health_changed`.- Cache node references with `@onready` and unique names. Do not call `get_node` every frame.- Keep the file's indentation. Godot's default is tabs. Do not convert a file to spaces. ## Godot - Use the Godot feature tag already in `project.godot`. Do not change it as a side effect.- A script assumes only the nodes in its own scene. Call down to children and signal up to parents.- Do not reach across the tree with absolute node paths. Do not add an autoload for one scene's state.- Use `_physics_process` for movement and `_process` otherwise. Multiply speeds by `delta`.- Do not edit the `.godot/` cache. Commit `project.godot`, scenes, scripts, and `.import` files.- Prefer containers and anchors for UI that must resize. Do not hard-code a full-screen layout in pixels. ## GUT - If the GUT addon is installed, extend `GutTest` and use `assert_eq` and `assert_true`. Do not print and eyeball.- Instance any scene the test needs inside the test. Do not require the editor to be open.- Do not add a second Godot test framework beside GUT. ## Godot project files - Do not introduce Node, Python, or another toolchain unless a subfolder already has it.- Do not commit the `.godot/` cache. Do commit `project.godot` and `.import` files. ## Testing expectations - When you fix a bug, add a test that fails before the fix and passes after, in the repo's current test style.- When you change behavior a caller can observe, update or add a test for that behavior.- Do not test private helpers, framework internals, or third-party libraries. ## Code style - Keep strict type and lint settings on. Do not weaken them to get a green build.- No new `any`, and no empty catch blocks. Prefer `unknown` and narrowing. Handle every fallible call.- Give exported functions an explicit type when the inferred type is not obvious.- Follow the repo formatter. Do not hand-format files the formatter owns.- Do not add comments that restate the code.- Comment only a constraint, invariant, or tradeoff the code itself cannot show.- No file-header banners and no changelog comments. ## Safety - Never commit `.env`, keystores, or credential files. When a new variable is required, add an empty placeholder to the example env file.- Do not disable authentication, authorization, or TLS checks to make a test pass.- Do not force-push, `reset --hard`, drop a database, or delete a directory tree unless the user asked for that exact action.- Do not edit vendored or generated output (`node_modules`, `dist`, `.next`, `vendor`, `Library`, `.godot`). Change the source and regenerate. ## Done when - The change does what was asked and nothing extra.- New or changed behavior is covered at the level in Testing expectations.- The commands in this file that apply to the touched files have been run, or you say which command you could not run.- The diff has no unrelated files, lockfile churn, or secrets.