From cf0cd749e968033858b6d3f7109be28dd8d545ce Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=92=D0=B8=D1=82=D0=B0=D0=BB=D0=B8=D0=B9=20=D0=9D=D0=B8?= =?UTF-8?q?=D0=BA=D0=B8=D1=82=D0=B5=D0=BD=D0=BA=D0=BE?= Date: Mon, 22 Jun 2026 14:42:41 +0300 Subject: [PATCH] =?UTF-8?q?chore:=20=D1=83=D0=B1=D1=80=D0=B0=D1=82=D1=8C?= =?UTF-8?q?=20=D0=BF=D1=80=D0=B0=D0=B2=D0=B8=D0=BB=D0=BE=20=D0=BF=D1=80?= =?UTF-8?q?=D0=BE=20=D1=82=D0=B8=D0=BF=D0=BE=D0=B3=D1=80=D0=B0=D1=84=D0=B8?= =?UTF-8?q?=D0=BA=D1=83=20=D0=B8=D0=B7=20=D0=B3=D0=BB=D0=BE=D0=B1=D0=B0?= =?UTF-8?q?=D0=BB=D1=8C=D0=BD=D1=8B=D1=85=20=D0=BF=D1=80=D0=B0=D0=B2=D0=B8?= =?UTF-8?q?=D0=BB=20=D0=B0=D0=B3=D0=B5=D0=BD=D1=82=D0=BE=D0=B2?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Удалён пункт Typography (дефис-минус вместо длинных тире), последующие пункты перенумерованы. Co-Authored-By: Claude --- home-configs/GLOBAL_RULES.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/home-configs/GLOBAL_RULES.md b/home-configs/GLOBAL_RULES.md index 0d8ae74..e6be725 100644 --- a/home-configs/GLOBAL_RULES.md +++ b/home-configs/GLOBAL_RULES.md @@ -77,13 +77,10 @@ The rules below are mandatory for every interaction and task. They are intention 3. **Plain git diff visibility:** All changes must remain visible to the user through the standard `git diff` command. Leave modified files in the working directory unstaged. Do not add files to the Git index with `git add` unless the user explicitly asks for staging, committing, or another action that requires staging, because staging hides changes from plain `git diff`. -4. **Typography:** - Always use the regular hyphen-minus (`-`) instead of long dash characters. - -5. **Project context:** +4. **Project context:** At the start of work, pay close attention to all provided project `.md` files, because they are provided automatically and contain the current repository's context and specifics. -6. **Reusable skills:** +5. **Reusable skills:** When the user repeats the same instruction, output format, correction, or workflow, treat it as a candidate for a reusable skill. Do not interrupt active work just to create a skill. Finish the current task first, then briefly propose the skill name, trigger description, and what files or tools it should contain.