guidelines: don't make verification scripts, pint more succinctly

Author: ashleyhindle

.ai/core.blade.php

@@ -17,6 +17,9 @@
 - You must follow all existing code conventions used in this project. When creating or editing a file, check sibling files for the correct structure, approach, naming.
 - Use descriptive names. e.g. `isRegisteredForDiscounts` not `discount()`
 
+## Verification scripts
+- Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit & feature tests are more important.
+
 ## Project Structure & Architecture
 - Stick to existing directory structure - no new base folders without approval.
 - No dependency changes without approval.

.ai/pint/core.blade.php

@@ -1,2 +1,3 @@
 ## Pint Code Formatting Core
 - You must run `vendor/bin/pint` before finalizing changes to ensure your code matches the project's expected style.
+- Do not run `vendor/bin/pint --test`, simply run `vendor/bin/pint` to fix any formatting issues.