Add reusable skills global rule

GLOBAL_RULES.md

@@ -82,3 +82,14 @@ The rules below are mandatory for every interaction and task. They are intention
 
 5. **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:**
+   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.
+
+   Do not create or edit skill files silently. Create or update a skill only after explicit user approval.
+
+   Keep skills focused: prefer several small skills over one broad skill. A useful skill should have a precise description for when to use it, short instructions for how to act, and reusable tools, templates, references, or examples when they make the result more stable.
+
+   If skill files are outside the current git repository, clearly state the exact paths changed and how the user can inspect them, because those changes are not visible in the project `git diff`.

README.md

@@ -108,6 +108,7 @@ exec bash
 3. Не выполнять `git add` без прямой просьбы, чтобы изменения оставались видны через обычный `git diff`.
 4. Использовать обычный дефис `-`, не em dash.
 5. В начале работы внимательно учитывать все проектные `.md` файлы.
+6. При повторяющихся инструкциях предлагать reusable skill, но создавать или менять skill-файлы только после явного согласия.
 
 Правило этого проекта: