Laravel rules file

---description: "Project rules for PHP, Laravel, Pest, Composer. Generated by RulePaste."alwaysApply: true--- # Project rules Stack: PHP, Laravel, Pest, Composer. 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 - Install PHP dependencies with `composer install`. Commit `composer.lock`.- Composer is the package manager. A package.json, if present, is only for frontend assets.- Prefer `composer run dev` when that script exists. Otherwise use `php artisan serve` for a local API.- Tests: `php artisan test`. Format changed PHP with `vendor/bin/pint` when Pint is installed.- Do not run `migrate` against a shared database unless the user asked for that. ## PHP - Match the PHP version in `composer.json`. Type new properties, parameters, and return values.- Keep `declare(strict_types=1);` if the file has it, and add it to new files when the package uses it.- PSR-12 formatting. Autoload through Composer. Do not `require` class files by path.- Do not hide errors with `@`. Queries use the query builder or bound parameters, never interpolated request data. ## Laravel - Follow the routing style this repo uses (`routes/*.php` or `bootstrap/app.php`). Do not invent a third style.- Controllers stay thin. Validate with a Form Request, not a long controller method.- Define Eloquent relationships on the model and eager-load with `with()` when a loop touches a relation.- Migrations are append-only. Create a new one with Artisan. Do not edit a migration that has run in production.- Call `config()` in application code. Call `env()` only inside config files.- Stay on the frontend already installed (Blade, Inertia, or Livewire). Use the auth starter already installed. Do not add a second one.- Put slow work on the queue if the project has one. Format changed PHP with Pint when `vendor/bin/pint` exists. ## Pest - Write `it()` or `test()` closures. Feature tests belong in `tests/Feature` and hit HTTP. Unit tests do not boot the whole framework for a pure class.- Create records with factories. Do not depend on rows that happen to exist locally.- Run `php artisan test`. Do not add PHPUnit classes beside Pest for the same area. ## Composer - Install PHP dependencies with `composer install`. Add packages with `composer require`. Commit `composer.lock`.- Do not load classes by hand. Autoload through Composer. ## 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: PHP, Laravel, Pest, Composer. 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 - Install PHP dependencies with `composer install`. Commit `composer.lock`.- Composer is the package manager. A package.json, if present, is only for frontend assets.- Prefer `composer run dev` when that script exists. Otherwise use `php artisan serve` for a local API.- Tests: `php artisan test`. Format changed PHP with `vendor/bin/pint` when Pint is installed.- Do not run `migrate` against a shared database unless the user asked for that. ## PHP - Match the PHP version in `composer.json`. Type new properties, parameters, and return values.- Keep `declare(strict_types=1);` if the file has it, and add it to new files when the package uses it.- PSR-12 formatting. Autoload through Composer. Do not `require` class files by path.- Do not hide errors with `@`. Queries use the query builder or bound parameters, never interpolated request data. ## Laravel - Follow the routing style this repo uses (`routes/*.php` or `bootstrap/app.php`). Do not invent a third style.- Controllers stay thin. Validate with a Form Request, not a long controller method.- Define Eloquent relationships on the model and eager-load with `with()` when a loop touches a relation.- Migrations are append-only. Create a new one with Artisan. Do not edit a migration that has run in production.- Call `config()` in application code. Call `env()` only inside config files.- Stay on the frontend already installed (Blade, Inertia, or Livewire). Use the auth starter already installed. Do not add a second one.- Put slow work on the queue if the project has one. Format changed PHP with Pint when `vendor/bin/pint` exists. ## Pest - Write `it()` or `test()` closures. Feature tests belong in `tests/Feature` and hit HTTP. Unit tests do not boot the whole framework for a pure class.- Create records with factories. Do not depend on rows that happen to exist locally.- Run `php artisan test`. Do not add PHPUnit classes beside Pest for the same area. ## Composer - Install PHP dependencies with `composer install`. Add packages with `composer require`. Commit `composer.lock`.- Do not load classes by hand. Autoload through Composer. ## 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: PHP, Laravel, Pest, Composer. 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 - Install PHP dependencies with `composer install`. Commit `composer.lock`.- Composer is the package manager. A package.json, if present, is only for frontend assets.- Prefer `composer run dev` when that script exists. Otherwise use `php artisan serve` for a local API.- Tests: `php artisan test`. Format changed PHP with `vendor/bin/pint` when Pint is installed.- Do not run `migrate` against a shared database unless the user asked for that. ## PHP - Match the PHP version in `composer.json`. Type new properties, parameters, and return values.- Keep `declare(strict_types=1);` if the file has it, and add it to new files when the package uses it.- PSR-12 formatting. Autoload through Composer. Do not `require` class files by path.- Do not hide errors with `@`. Queries use the query builder or bound parameters, never interpolated request data. ## Laravel - Follow the routing style this repo uses (`routes/*.php` or `bootstrap/app.php`). Do not invent a third style.- Controllers stay thin. Validate with a Form Request, not a long controller method.- Define Eloquent relationships on the model and eager-load with `with()` when a loop touches a relation.- Migrations are append-only. Create a new one with Artisan. Do not edit a migration that has run in production.- Call `config()` in application code. Call `env()` only inside config files.- Stay on the frontend already installed (Blade, Inertia, or Livewire). Use the auth starter already installed. Do not add a second one.- Put slow work on the queue if the project has one. Format changed PHP with Pint when `vendor/bin/pint` exists. ## Pest - Write `it()` or `test()` closures. Feature tests belong in `tests/Feature` and hit HTTP. Unit tests do not boot the whole framework for a pure class.- Create records with factories. Do not depend on rows that happen to exist locally.- Run `php artisan test`. Do not add PHPUnit classes beside Pest for the same area. ## Composer - Install PHP dependencies with `composer install`. Add packages with `composer require`. Commit `composer.lock`.- Do not load classes by hand. Autoload through Composer. ## 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 PHP, Laravel, Pest, Composer. Generated by RulePaste."--- # Project rules Stack: PHP, Laravel, Pest, Composer. 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 - Install PHP dependencies with `composer install`. Commit `composer.lock`.- Composer is the package manager. A package.json, if present, is only for frontend assets.- Prefer `composer run dev` when that script exists. Otherwise use `php artisan serve` for a local API.- Tests: `php artisan test`. Format changed PHP with `vendor/bin/pint` when Pint is installed.- Do not run `migrate` against a shared database unless the user asked for that. ## PHP - Match the PHP version in `composer.json`. Type new properties, parameters, and return values.- Keep `declare(strict_types=1);` if the file has it, and add it to new files when the package uses it.- PSR-12 formatting. Autoload through Composer. Do not `require` class files by path.- Do not hide errors with `@`. Queries use the query builder or bound parameters, never interpolated request data. ## Laravel - Follow the routing style this repo uses (`routes/*.php` or `bootstrap/app.php`). Do not invent a third style.- Controllers stay thin. Validate with a Form Request, not a long controller method.- Define Eloquent relationships on the model and eager-load with `with()` when a loop touches a relation.- Migrations are append-only. Create a new one with Artisan. Do not edit a migration that has run in production.- Call `config()` in application code. Call `env()` only inside config files.- Stay on the frontend already installed (Blade, Inertia, or Livewire). Use the auth starter already installed. Do not add a second one.- Put slow work on the queue if the project has one. Format changed PHP with Pint when `vendor/bin/pint` exists. ## Pest - Write `it()` or `test()` closures. Feature tests belong in `tests/Feature` and hit HTTP. Unit tests do not boot the whole framework for a pure class.- Create records with factories. Do not depend on rows that happen to exist locally.- Run `php artisan test`. Do not add PHPUnit classes beside Pest for the same area. ## Composer - Install PHP dependencies with `composer install`. Add packages with `composer require`. Commit `composer.lock`.- Do not load classes by hand. Autoload through Composer. ## 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: PHP, Laravel, Pest, Composer. 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 - Install PHP dependencies with `composer install`. Commit `composer.lock`.- Composer is the package manager. A package.json, if present, is only for frontend assets.- Prefer `composer run dev` when that script exists. Otherwise use `php artisan serve` for a local API.- Tests: `php artisan test`. Format changed PHP with `vendor/bin/pint` when Pint is installed.- Do not run `migrate` against a shared database unless the user asked for that. ## PHP - Match the PHP version in `composer.json`. Type new properties, parameters, and return values.- Keep `declare(strict_types=1);` if the file has it, and add it to new files when the package uses it.- PSR-12 formatting. Autoload through Composer. Do not `require` class files by path.- Do not hide errors with `@`. Queries use the query builder or bound parameters, never interpolated request data. ## Laravel - Follow the routing style this repo uses (`routes/*.php` or `bootstrap/app.php`). Do not invent a third style.- Controllers stay thin. Validate with a Form Request, not a long controller method.- Define Eloquent relationships on the model and eager-load with `with()` when a loop touches a relation.- Migrations are append-only. Create a new one with Artisan. Do not edit a migration that has run in production.- Call `config()` in application code. Call `env()` only inside config files.- Stay on the frontend already installed (Blade, Inertia, or Livewire). Use the auth starter already installed. Do not add a second one.- Put slow work on the queue if the project has one. Format changed PHP with Pint when `vendor/bin/pint` exists. ## Pest - Write `it()` or `test()` closures. Feature tests belong in `tests/Feature` and hit HTTP. Unit tests do not boot the whole framework for a pure class.- Create records with factories. Do not depend on rows that happen to exist locally.- Run `php artisan test`. Do not add PHPUnit classes beside Pest for the same area. ## Composer - Install PHP dependencies with `composer install`. Add packages with `composer require`. Commit `composer.lock`.- Do not load classes by hand. Autoload through Composer. ## 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: PHP, Laravel, Pest, Composer. 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 - Install PHP dependencies with `composer install`. Commit `composer.lock`.- Composer is the package manager. A package.json, if present, is only for frontend assets.- Prefer `composer run dev` when that script exists. Otherwise use `php artisan serve` for a local API.- Tests: `php artisan test`. Format changed PHP with `vendor/bin/pint` when Pint is installed.- Do not run `migrate` against a shared database unless the user asked for that. ## PHP - Match the PHP version in `composer.json`. Type new properties, parameters, and return values.- Keep `declare(strict_types=1);` if the file has it, and add it to new files when the package uses it.- PSR-12 formatting. Autoload through Composer. Do not `require` class files by path.- Do not hide errors with `@`. Queries use the query builder or bound parameters, never interpolated request data. ## Laravel - Follow the routing style this repo uses (`routes/*.php` or `bootstrap/app.php`). Do not invent a third style.- Controllers stay thin. Validate with a Form Request, not a long controller method.- Define Eloquent relationships on the model and eager-load with `with()` when a loop touches a relation.- Migrations are append-only. Create a new one with Artisan. Do not edit a migration that has run in production.- Call `config()` in application code. Call `env()` only inside config files.- Stay on the frontend already installed (Blade, Inertia, or Livewire). Use the auth starter already installed. Do not add a second one.- Put slow work on the queue if the project has one. Format changed PHP with Pint when `vendor/bin/pint` exists. ## Pest - Write `it()` or `test()` closures. Feature tests belong in `tests/Feature` and hit HTTP. Unit tests do not boot the whole framework for a pure class.- Create records with factories. Do not depend on rows that happen to exist locally.- Run `php artisan test`. Do not add PHPUnit classes beside Pest for the same area. ## Composer - Install PHP dependencies with `composer install`. Add packages with `composer require`. Commit `composer.lock`.- Do not load classes by hand. Autoload through Composer. ## 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: PHP, Laravel, Pest, Composer. 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 - Install PHP dependencies with `composer install`. Commit `composer.lock`.- Composer is the package manager. A package.json, if present, is only for frontend assets.- Prefer `composer run dev` when that script exists. Otherwise use `php artisan serve` for a local API.- Tests: `php artisan test`. Format changed PHP with `vendor/bin/pint` when Pint is installed.- Do not run `migrate` against a shared database unless the user asked for that. ## PHP - Match the PHP version in `composer.json`. Type new properties, parameters, and return values.- Keep `declare(strict_types=1);` if the file has it, and add it to new files when the package uses it.- PSR-12 formatting. Autoload through Composer. Do not `require` class files by path.- Do not hide errors with `@`. Queries use the query builder or bound parameters, never interpolated request data. ## Laravel - Follow the routing style this repo uses (`routes/*.php` or `bootstrap/app.php`). Do not invent a third style.- Controllers stay thin. Validate with a Form Request, not a long controller method.- Define Eloquent relationships on the model and eager-load with `with()` when a loop touches a relation.- Migrations are append-only. Create a new one with Artisan. Do not edit a migration that has run in production.- Call `config()` in application code. Call `env()` only inside config files.- Stay on the frontend already installed (Blade, Inertia, or Livewire). Use the auth starter already installed. Do not add a second one.- Put slow work on the queue if the project has one. Format changed PHP with Pint when `vendor/bin/pint` exists. ## Pest - Write `it()` or `test()` closures. Feature tests belong in `tests/Feature` and hit HTTP. Unit tests do not boot the whole framework for a pure class.- Create records with factories. Do not depend on rows that happen to exist locally.- Run `php artisan test`. Do not add PHPUnit classes beside Pest for the same area. ## Composer - Install PHP dependencies with `composer install`. Add packages with `composer require`. Commit `composer.lock`.- Do not load classes by hand. Autoload through Composer. ## 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.