From 3564235d4538767ad69d2a222ed7c09e3e376d22 Mon Sep 17 00:00:00 2001 From: Igor Lebedev Date: Tue, 15 Jul 2025 15:57:09 +0500 Subject: [PATCH 1/4] docs: formalize AI fallback rule and cross-link in README, onboarding, best practices, .rules, memory-bank --- .cursor/rules/README.md | 5 + .gitmodules | 6 + .rules/ai-fallback.rules.md | 9 + README.md | 20 ++ .../cursor-rules-system.md | 305 ++++++++++++++++++ docs/onboarding.md | 6 + .../chrome-extension-boilerplate-react-vite | 1 + external/sidepanel-template | 1 + memory-bank/activeContext.md | 11 +- 9 files changed, 363 insertions(+), 1 deletion(-) create mode 100644 .gitmodules create mode 100644 .rules/ai-fallback.rules.md create mode 100644 docs/for-ai-best-practices/cursor-rules-system.md create mode 100644 docs/onboarding.md create mode 160000 external/chrome-extension-boilerplate-react-vite create mode 160000 external/sidepanel-template diff --git a/.cursor/rules/README.md b/.cursor/rules/README.md index e1517567..be29a96c 100644 --- a/.cursor/rules/README.md +++ b/.cursor/rules/README.md @@ -82,6 +82,11 @@ This directory contains all rules and standards for automation and AI assistants workflow.mdc ``` +--- +## AI Fallback Rule + +If an AI agent cannot answer a question from its own memory-bank, it must first check the .rules directory, then the memory-bank directory. See [.rules/ai-fallback.rules.md](../../.rules/ai-fallback.rules.md). +--- ## How to Use - The AI assistant should always refer to specific .mdc files when making decisions diff --git a/.gitmodules b/.gitmodules new file mode 100644 index 00000000..1ea58a33 --- /dev/null +++ b/.gitmodules @@ -0,0 +1,6 @@ +[submodule "external/sidepanel-template"] + path = external/sidepanel-template + url = https://github.com/QizhengMo/chrome-extension-sidepanel-template.git +[submodule "external/chrome-extension-boilerplate-react-vite"] + path = external/chrome-extension-boilerplate-react-vite + url = https://github.com/Jonghakseo/chrome-extension-boilerplate-react-vite diff --git a/.rules/ai-fallback.rules.md b/.rules/ai-fallback.rules.md new file mode 100644 index 00000000..de965e7e --- /dev/null +++ b/.rules/ai-fallback.rules.md @@ -0,0 +1,9 @@ +# AI Fallback Rule + +**Правило:** +Если возникает вопрос, на который нет ответа в AI memory-bank, необходимо: +1. Сначала обращаться к сведениям в папке .rules проекта. +2. Если нужной информации нет в .rules, обращаться к сведениям в папке memory-bank проекта (особенно к архитектурным и контекстным файлам). + +**Приоритет:** +Это правило приоритетно для всех будущих консультаций и автоматизаций. \ No newline at end of file diff --git a/README.md b/README.md index cb705652..419ae419 100755 --- a/README.md +++ b/README.md @@ -58,6 +58,20 @@ pnpm build pnpm zip ``` +**Полный список команд для сборки, очистки, запуска и разработки:** +- [Developer Commands (developer-commands.md)](docs/developer-commands.md) + +#### Dev-команды для отдельных пакетов/страниц + +```bash +# Быстрый запуск разработки только для одной страницы/пакета: +pnpm --filter pages/options dev +pnpm --filter pages/side-panel dev +pnpm --filter packages/ui dev +``` +- Используйте эти команды для ускорения разработки, если меняются только отдельные части проекта. +- Можно запускать несколько dev-серверов параллельно для разных страниц. + ### Тестирование ```bash # E2E тесты @@ -161,3 +175,9 @@ MIT License - см. файл [LICENSE](LICENSE) **Важно:** - Все тестовые скрипты и логи рекомендуется запускать и смотреть именно в этой вкладке или через боковую панель расширения. - Название вкладки уникальное, чтобы не путать с системной вкладкой DevTools. + +--- +## AI Knowledge Fallback + +If the AI agent cannot answer a question from its own memory-bank, it must first consult the .rules directory, and if no answer is found there, then consult the memory-bank directory. See [.rules/ai-fallback.rules.md](.rules/ai-fallback.rules.md) for details. +--- diff --git a/docs/for-ai-best-practices/cursor-rules-system.md b/docs/for-ai-best-practices/cursor-rules-system.md new file mode 100644 index 00000000..d87123b9 --- /dev/null +++ b/docs/for-ai-best-practices/cursor-rules-system.md @@ -0,0 +1,305 @@ +# Cursor Rules System — Modular, AI-First, Automated + +> This is a proven, modular rule/documentation system. Copy/adapt for any project. + +This document describes the principles, structure, automation, and best practices for organizing `.cursor/rules/` in a modern, AI-friendly, and scalable way. Use this as a template to implement the same system in any project. + +--- + +## 1. Introduction + +The `.cursor/rules/` system is designed for: +- Maximum clarity and maintainability for both humans and AI assistants +- Fast navigation, search, and automation +- Seamless scaling as the number of rules grows +- Full compatibility with AI-first workflows and best practices +- Automated cross-referencing and documentation + +--- + +## 2. Core Principles & Rationale + +- **English-First**: All rules, docs, and comments are in English for maximum AI and team compatibility. (User commands may remain in the original language for clarity.) +- **One Rule — One File**: Each `.mdc` file contains exactly one rule or standard. This enables modularity, easy linking, and granular automation. +- **Topic-Based Folders**: Rules are grouped by topic (e.g., `dev-principles/`, `architecture/`, `plugin/`, `ui/`, `workflow/`, `doc/`). +- **Category Expansion**: For large projects, use more granular folders: `security/`, `workflow/`, `code-style/`, `automation/`, `memorybank/`, `dev-experience/`. +- **Explicit Metadata**: Each rule file includes `description:`, `globs:`, `alwaysApply:`, and (optionally) `related:` and `examples:`. +- **Cross-Reference Policy**: Every rule or doc should include links to all relevant files (related rules, onboarding, progress, user commands, architecture, graveyard, etc.) in a `Cross-References` section. +- **Automation-First**: Index, summary, and cross-references are auto-generated and checked by scripts for all `.md`/`.mdc` files. +- **AI-First Documentation**: All rules are written with clarity for both humans and AI, with explicit logic, rationale, and cross-links. + +--- + +## 3. Directory & File Structure + +``` +.cursor/ + rules/ + README.md + index.mdc + dev-principles/ + 01-do-no-harm.mdc + ... + architecture/ + project-structure.mdc + ... + plugin/ + structure.mdc + ... + ui/ + accessibility.mdc + ... + workflow/ + branches.mdc + ... + doc/ + ai-first.mdc + user-commands.mdc + ... + security/ + security-principles.mdc + ... + code-style/ + typescript-best-practices.mdc + ... + automation/ + automation.mdc + ... + memorybank/ + memorybank-quality.mdc + knowledge-map.mdc + ... + dev-experience/ + user-commands.mdc + ... +``` + +--- + +## 4. Rule File Format (`.mdc`) + +Each rule file must contain: +- `# Heading` — short, clear title +- **Category** (optional but recommended for large projects) +- Main rule body (bulleted or short paragraphs) +- **Rationale** — why this rule is important (AI/Dev/Team context) +- **Example** — code/config/example if relevant +- `related:` — (optional) list of related rule files +- **Cross-References** — (optional but recommended) links to onboarding, progress, user commands, architecture, graveyard, etc. +- `description:` — short summary for index/search +- `globs:` — file globs for rule application +- `alwaysApply:` — usually `false` +- `---` — end of metadata + +**Example:** +``` +# Plugin Error Handling + +**Category:** plugin + +- Graceful Degradation: Continue working with reduced functionality +- User Feedback: Provide clear error messages to users +- Logging: Log errors for debugging without exposing sensitive data +- Fallbacks: Implement fallback mechanisms for critical features +- Recovery: Automatic retry mechanisms where appropriate + +## Rationale +Clear error handling ensures plugins do not break the user experience and are easy to debug for both developers and AI. + +## Example +If a plugin fails, show a user-friendly error and log the details for debugging. + +related: + - plugin-security.mdc + - architecture-error-handling.mdc + +## Cross-References +- [Onboarding](../../docs/onboarding.md) — for new developer guidance +- [Progress](../../memory-bank/progress.md) — for current project status +- [User Commands](../../docs/USER_COMMANDS.md) — for automation commands +- [Architecture](../../memory-bank/codebase-architecture.md) — for system overview + +description: Error handling requirements for all plugins +globs: + - public/plugins/* +alwaysApply: false +--- +``` + +--- + +## 5. Automation & CLI + +- **CLI Scripts** (in `.cursor/rules/`): + - `create-rule.cjs` — Interactive CLI to create a new rule file from a template. Updates index/README automatically. + - `generate-rules-index.cjs` — Scans all `.mdc` files (recursively) and regenerates `index.mdc` and the structure section in `README.md`. + - `check-rules-structure.cjs` — Validates all `.mdc` files for required sections, uniqueness, and valid related links. Used in CI. +- **Advanced CLI/Helper Scripts** (optional): + - `list` — Show structure of all rules by folder + - `search ` — Search rules by keyword + - `add ` — Create a new rule from template + - `edit ` — Edit a rule by relative path + - `generate-toc` — Recursively updates ToC, summary, and required cross-references for all `.md`/`.mdc` files + - `security-audit` — Checks Docker, .env, dependencies, outputs `audit-report.md` +- **Usage:** + - `node .cursor/rules/create-rule.cjs` + - `node .cursor/rules/generate-rules-index.cjs` + - `node .cursor/rules/check-rules-structure.cjs` + +--- + +## 6. CI Integration + +- **GitHub Actions** workflow (`.github/workflows/rules-check.yml`): + - Runs on every push/PR to `.cursor/rules/` + - Regenerates index/README and checks for uncommitted changes + - Validates all rules for structure and related links + - Fails the build if any issues are found +- **Advanced CI (optional):** + - Runs ToC/cross-reference automation, security/performance audit, and roadmap sync + +**Example:** +```yaml +name: Rules Structure Check +on: + push: + paths: + - '.cursor/rules/**' + pull_request: + paths: + - '.cursor/rules/**' +jobs: + check-rules: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + - name: Setup Node.js + uses: actions/setup-node@v3 + with: + node-version: '18' + - name: Generate index and README structure + run: node .cursor/rules/generate-rules-index.cjs + - name: Check for uncommitted changes + run: | + git diff --exit-code || (echo 'index.mdc or README.md is outdated. Please run generate-rules-index.cjs and commit the result.' && exit 1) + - name: Check rules structure + run: node .cursor/rules/check-rules-structure.cjs +``` + +--- + +## 7. How to Add/Update Rules + +- Use `create-rule.cjs` to add new rules (enforces template and updates navigation) +- Always provide a clear heading, rationale, example, and cross-references +- Use English for all content except user commands (which may remain in the original language) +- Run `generate-rules-index.cjs` after any manual changes +- Run `check-rules-structure.cjs` to validate before commit/PR +- For advanced projects, use the CLI/ToC/cross-reference automation and developer helper scripts + +--- + +## 8. Safe Delete & Notification + +- All automation scripts and CI/CD must use safe delete functions to prevent accidental removal of protected directories. +- See [Safe Delete Best Practice](./README.md) and [CI Integration](./ci-integration.md) for implementation details. + +--- + +## 9. How to Port to Another Project + +1. Copy `.cursor/rules/` (with all subfolders, scripts, and templates) to the new project +2. Add the GitHub Actions workflow to `.github/workflows/` +3. Update or add rules as needed for the new context +4. Run the CLI scripts to generate index/README and validate structure +5. (Optional) Update globs and descriptions for the new codebase +6. Document any project-specific conventions in `README.md` +7. (Optional) Add advanced automation for ToC, cross-references, and roadmap sync + +--- + +## 9. Advanced Practices: Roadmap & Synchronization + +- **User-Facing Roadmap:** + - All current and planned automation, DevOps, and AI improvements are published in `docs/PLANS.md` for easy access by users and contributors. + - This file is always in sync with the technical/AI roadmap in `memory-bank/progress.md`. +- **AI/Dev Roadmap:** + - `memory-bank/progress.md` contains the full, detailed, and always up-to-date list of planned improvements, technical context, and project status for AI/LLM and the core team. +- **Synchronization Mechanism:** + - The section `## Planned Automation & Improvements` is automatically synchronized between `memory-bank/progress.md` and `docs/PLANS.md` using a script (e.g., `tools/sync_plans.py`). + - This script can be run manually or automatically in CI. + - Any update to plans in one file is reflected in the other, ensuring both user and AI/Dev audiences always see the latest roadmap. +- **Best Practice:** + - Always update plans in `memory-bank/progress.md` (the source of truth), then run the sync script or let CI handle it. + - Reference `docs/PLANS.md` in onboarding, README, and user docs for maximum transparency. + +--- + +## 10. FAQ & Troubleshooting + +- **Q: Why English?** + - For maximum AI compatibility and international team support +- **Q: Why one rule per file?** + - For modularity, easy linking, and granular automation +- **Q: What if I need a new topic?** + - Just create a new folder and add rules there +- **Q: How to avoid duplicates?** + - Use the CLI search and always check before adding +- **Q: How to update navigation?** + - Run the ToC/summary automation after any changes + +--- + +## 11. Appendix: Templates & Examples + +**Rule Template:** +``` +# [Rule Title] + +**Category:** [security|workflow|code-style|automation|memorybank|dev-experience] + +## Rule +Describe the rule clearly and concisely. + +## Rationale +Why is this rule important? (AI/Dev/Team context) + +## Example +Provide a code/config/example if relevant. + +related: + - [other-rule.mdc] + +## Cross-References +- [Related Rule 1](../security/another-rule.mdc) — similar security policy +- [Graveyard](../../memory-bank/graveyard.md) — see failed solutions +- [Onboarding](../../docs/onboarding.md) — for new developer guidance +- [Progress](../../memory-bank/progress.md) — for current project status +- [User Commands](../../docs/USER_COMMANDS.md) — for automation commands +- [Architecture](../../memory-bank/codebase-architecture.md) — for system overview + +description: [Short summary] +globs: + - [glob patterns] +alwaysApply: false +--- +``` + +**CLI Usage:** +- `node .cursor/rules/create-rule.cjs` +- `node .cursor/rules/generate-rules-index.cjs` +- `node .cursor/rules/check-rules-structure.cjs` + +--- + +**This system is proven, scalable, and AI-friendly. Copy, adapt, and use it in any project!** + +--- +### AI Fallback Logic + +If an answer is not found in the AI memory-bank, the agent must: +1. First, check the .rules directory for relevant rules. +2. If not found, check the memory-bank directory (especially architecture and context files). + +See [.rules/ai-fallback.rules.md](../../.rules/ai-fallback.rules.md) for the canonical rule. +--- \ No newline at end of file diff --git a/docs/onboarding.md b/docs/onboarding.md new file mode 100644 index 00000000..9fb3e0d5 --- /dev/null +++ b/docs/onboarding.md @@ -0,0 +1,6 @@ + +--- +## Working with AI: Fallback Rule + +When working with the AI assistant, if it cannot answer from its own memory, it will first consult the .rules directory, then the memory-bank directory. This ensures all project knowledge is accessible and up-to-date. See [.rules/ai-fallback.rules.md](../.rules/ai-fallback.rules.md). +--- \ No newline at end of file diff --git a/external/chrome-extension-boilerplate-react-vite b/external/chrome-extension-boilerplate-react-vite new file mode 160000 index 00000000..2087bc9c --- /dev/null +++ b/external/chrome-extension-boilerplate-react-vite @@ -0,0 +1 @@ +Subproject commit 2087bc9ce162cf84120588a6189b2b53437c43b6 diff --git a/external/sidepanel-template b/external/sidepanel-template new file mode 160000 index 00000000..0fd7acde --- /dev/null +++ b/external/sidepanel-template @@ -0,0 +1 @@ +Subproject commit 0fd7acdebf993cfc2fb78a8614619a839acfd9da diff --git a/memory-bank/activeContext.md b/memory-bank/activeContext.md index e9334ae8..50e68d4e 100644 --- a/memory-bank/activeContext.md +++ b/memory-bank/activeContext.md @@ -116,7 +116,7 @@ ## Команды и процессы ### Сборка проекта -```bash + ```bash # Сборка всех страниц pnpm run build @@ -172,3 +172,12 @@ pnpm run dev 3. Проверить работу в обеих темах 4. Протестировать все интерактивные элементы 5. Выявить и исправить ошибки отображения + +--- +## Архитектура: Sidepanel и контекстная логика + +- Sidepanel расширения открывается и закрывается пользователем сразу для всех вкладок браузера (через клик по иконке расширения). +- Содержимое боковой панели зависит от текущей web-страницы (адреса): если открыт ozon.ru, в списке доступных плагинов появляется карточка ozon.ru, при нажатии на которую появляется чат с этим плагином. +- Список доступных плагинов в сайдпанели зависит от разрешений, указанных в манифестах плагинов: например, карточка плагина ozon.ru появляется только на домене ozon.ru, если в его манифесте есть соответствующее разрешение. +- Сайдпанель не работает как отдельная extension page, а всегда контекстно привязана к активной вкладке и сайту. +--- From b0fdf52c07972450b496ae7c5284c30bf4af96a5 Mon Sep 17 00:00:00 2001 From: Igor Lebedev Date: Tue, 15 Jul 2025 16:16:55 +0500 Subject: [PATCH 2/4] refactor(rules): move ai-fallback and git-workflow rules to thematic subfolders, update all links --- .cursor/rules/README.md | 2 +- .cursor/rules/dev/git-workflow.rules.md | 6 ++++++ .cursor/rules/doc/ai-fallback.rules.md | 9 +++++++++ README.md | 2 +- docs/for-ai-best-practices/cursor-rules-system.md | 2 +- docs/onboarding.md | 2 +- 6 files changed, 19 insertions(+), 4 deletions(-) create mode 100644 .cursor/rules/dev/git-workflow.rules.md create mode 100644 .cursor/rules/doc/ai-fallback.rules.md diff --git a/.cursor/rules/README.md b/.cursor/rules/README.md index be29a96c..6d88bfc6 100644 --- a/.cursor/rules/README.md +++ b/.cursor/rules/README.md @@ -85,7 +85,7 @@ This directory contains all rules and standards for automation and AI assistants --- ## AI Fallback Rule -If an AI agent cannot answer a question from its own memory-bank, it must first check the .rules directory, then the memory-bank directory. See [.rules/ai-fallback.rules.md](../../.rules/ai-fallback.rules.md). +If an AI agent cannot answer a question from its own memory-bank, it must first check the .rules directory, then the memory-bank directory. See [doc/ai-fallback.rules.md](./doc/ai-fallback.rules.md). --- ## How to Use diff --git a/.cursor/rules/dev/git-workflow.rules.md b/.cursor/rules/dev/git-workflow.rules.md new file mode 100644 index 00000000..2eac1107 --- /dev/null +++ b/.cursor/rules/dev/git-workflow.rules.md @@ -0,0 +1,6 @@ +# Git Workflow Rule + +**Rule:** +- Only merge into main from develop. +- All feature, fix, and doc branches must be merged into develop first, never directly into main. +- This rule is mandatory for all changes and pull requests. \ No newline at end of file diff --git a/.cursor/rules/doc/ai-fallback.rules.md b/.cursor/rules/doc/ai-fallback.rules.md new file mode 100644 index 00000000..de965e7e --- /dev/null +++ b/.cursor/rules/doc/ai-fallback.rules.md @@ -0,0 +1,9 @@ +# AI Fallback Rule + +**Правило:** +Если возникает вопрос, на который нет ответа в AI memory-bank, необходимо: +1. Сначала обращаться к сведениям в папке .rules проекта. +2. Если нужной информации нет в .rules, обращаться к сведениям в папке memory-bank проекта (особенно к архитектурным и контекстным файлам). + +**Приоритет:** +Это правило приоритетно для всех будущих консультаций и автоматизаций. \ No newline at end of file diff --git a/README.md b/README.md index 419ae419..1d1ae5da 100755 --- a/README.md +++ b/README.md @@ -179,5 +179,5 @@ MIT License - см. файл [LICENSE](LICENSE) --- ## AI Knowledge Fallback -If the AI agent cannot answer a question from its own memory-bank, it must first consult the .rules directory, and if no answer is found there, then consult the memory-bank directory. See [.rules/ai-fallback.rules.md](.rules/ai-fallback.rules.md) for details. +If the AI agent cannot answer a question from its own memory-bank, it must first consult the .cursor/rules directory, and if no answer is found there, then consult the memory-bank directory. See [.cursor/rules/doc/ai-fallback.rules.md](.cursor/rules/doc/ai-fallback.rules.md) for details. --- diff --git a/docs/for-ai-best-practices/cursor-rules-system.md b/docs/for-ai-best-practices/cursor-rules-system.md index d87123b9..7c1e6b51 100644 --- a/docs/for-ai-best-practices/cursor-rules-system.md +++ b/docs/for-ai-best-practices/cursor-rules-system.md @@ -301,5 +301,5 @@ If an answer is not found in the AI memory-bank, the agent must: 1. First, check the .rules directory for relevant rules. 2. If not found, check the memory-bank directory (especially architecture and context files). -See [.rules/ai-fallback.rules.md](../../.rules/ai-fallback.rules.md) for the canonical rule. +See [.cursor/rules/doc/ai-fallback.rules.md](../../.cursor/rules/doc/ai-fallback.rules.md) for the canonical rule. --- \ No newline at end of file diff --git a/docs/onboarding.md b/docs/onboarding.md index 9fb3e0d5..d33eddf2 100644 --- a/docs/onboarding.md +++ b/docs/onboarding.md @@ -2,5 +2,5 @@ --- ## Working with AI: Fallback Rule -When working with the AI assistant, if it cannot answer from its own memory, it will first consult the .rules directory, then the memory-bank directory. This ensures all project knowledge is accessible and up-to-date. See [.rules/ai-fallback.rules.md](../.rules/ai-fallback.rules.md). +When working with the AI assistant, if it cannot answer from its own memory, it will first consult the .rules directory, then the memory-bank directory. This ensures all project knowledge is accessible and up-to-date. See [.cursor/rules/doc/ai-fallback.rules.md](../.cursor/rules/doc/ai-fallback.rules.md). --- \ No newline at end of file From 9288fca9766e4464727e4111281b691dda6178bf Mon Sep 17 00:00:00 2001 From: Igor Lebedev Date: Tue, 15 Jul 2025 18:37:20 +0500 Subject: [PATCH 3/4] docs: add explicit branch protection and pre-push hook instructions to onboarding and git workflow rules --- .cursor/rules/dev/git-workflow.rules.md | 8 +++++++- docs/onboarding.md | 13 +++++++++++++ 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/.cursor/rules/dev/git-workflow.rules.md b/.cursor/rules/dev/git-workflow.rules.md index 2eac1107..e6a28b71 100644 --- a/.cursor/rules/dev/git-workflow.rules.md +++ b/.cursor/rules/dev/git-workflow.rules.md @@ -3,4 +3,10 @@ **Rule:** - Only merge into main from develop. - All feature, fix, and doc branches must be merged into develop first, never directly into main. -- This rule is mandatory for all changes and pull requests. \ No newline at end of file +- This rule is mandatory for all changes and pull requests. + +--- +## Enforcement +- Local pre-push hook (.husky/pre-push) blocks direct push to main and develop. +- GitHub branch protection prevents direct push and enforces PRs from develop only. +--- \ No newline at end of file diff --git a/docs/onboarding.md b/docs/onboarding.md index d33eddf2..da695aa8 100644 --- a/docs/onboarding.md +++ b/docs/onboarding.md @@ -3,4 +3,17 @@ ## Working with AI: Fallback Rule When working with the AI assistant, if it cannot answer from its own memory, it will first consult the .rules directory, then the memory-bank directory. This ensures all project knowledge is accessible and up-to-date. See [.cursor/rules/doc/ai-fallback.rules.md](../.cursor/rules/doc/ai-fallback.rules.md). +--- + +--- +## Branch Protection: main & develop + +- Direct push to main and develop is forbidden (enforced both locally and on GitHub). +- All changes must go through feature/fix/doc branches, merged into develop, and only then into main via PR. +- Local pre-push hook (.husky/pre-push) blocks direct push to main and develop: + ```sh + #!/bin/sh + bash bash-scripts/prevent-main-develop-push.sh + ``` +- See [.cursor/rules/dev/git-workflow.rules.md](../.cursor/rules/dev/git-workflow.rules.md) for details. --- \ No newline at end of file From 05d299ef74fb7e694fb2f7f9750aecde47ecfffa Mon Sep 17 00:00:00 2001 From: Igor Lebedev Date: Wed, 16 Jul 2025 00:18:51 +0500 Subject: [PATCH 4/4] chore: save local changes to rules and activeContext after PR merge --- .cursor/rules/README.md | 6 ++++++ memory-bank/activeContext.md | 5 +++++ 2 files changed, 11 insertions(+) diff --git a/.cursor/rules/README.md b/.cursor/rules/README.md index 6d88bfc6..82266d6b 100644 --- a/.cursor/rules/README.md +++ b/.cursor/rules/README.md @@ -88,6 +88,12 @@ This directory contains all rules and standards for automation and AI assistants If an AI agent cannot answer a question from its own memory-bank, it must first check the .rules directory, then the memory-bank directory. See [doc/ai-fallback.rules.md](./doc/ai-fallback.rules.md). --- +--- +## Main GitHub Repository + +https://github.com/LebedevIV/agent-plugins-platform-boilerplate +--- + ## How to Use - The AI assistant should always refer to specific .mdc files when making decisions - To add a new rule: create a separate .mdc file in the appropriate section (preferably via the CLI) diff --git a/memory-bank/activeContext.md b/memory-bank/activeContext.md index 50e68d4e..561e34c1 100644 --- a/memory-bank/activeContext.md +++ b/memory-bank/activeContext.md @@ -1,3 +1,8 @@ + +--- +**Main GitHub Repository:** https://github.com/LebedevIV/agent-plugins-platform-boilerplate +--- + # Активный контекст разработки ## Текущий статус проекта