From a5b9afafcb9e430ed56432d12b5adb9cfc9b59d1 Mon Sep 17 00:00:00 2001
From: zhom <2717306+zhom@users.noreply.github.com>
Date: Sun, 8 Jun 2025 17:06:10 +0400
Subject: [PATCH] docs: update agent instructions

---
 .cursor/rules/tests-and-linting-after-changes.mdc | 2 +-
 AI_INSTRUCTIONS.md                                | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.cursor/rules/tests-and-linting-after-changes.mdc b/.cursor/rules/tests-and-linting-after-changes.mdc
index 4074ec4..8b391a0 100644
--- a/.cursor/rules/tests-and-linting-after-changes.mdc
+++ b/.cursor/rules/tests-and-linting-after-changes.mdc
@@ -3,4 +3,4 @@ description:
 globs: 
 alwaysApply: true
 ---
-After your changes, instead of running specific tests or linting specific files, run "pnpm format && pnpm lint && pnpm test"
\ No newline at end of file
+After your changes, instead of running specific tests or linting specific files, run "pnpm format && pnpm lint && pnpm test". It means that you first format the code, then lint it, then test it, so that no part is broken after your changes.
\ No newline at end of file
diff --git a/AI_INSTRUCTIONS.md b/AI_INSTRUCTIONS.md
index 97e84f9..cd3ccc9 100644
--- a/AI_INSTRUCTIONS.md
+++ b/AI_INSTRUCTIONS.md
@@ -1,5 +1,5 @@
 # Instructions for AI Agents
 
-- If you want to run tests, only ever run them as "pnpm format && pnpm lint && pnpm test".
+- After your changes, instead of running specific tests or linting specific files, run "pnpm format && pnpm lint && pnpm test". It means that you first format the code, then lint it, then test it, so that no part is broken after your changes.
 - Don't leave comments that don't add value
 - Do not duplicate code unless you have a very good reason to do so. It is important that the same logic is not duplicated multiple times