Improved AI.md

Author: ivanskv2000

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,50 +1,17 @@
-## 📌 Pull Request Title
+## ✨ Overview
 
-<!-- 
-Use Conventional Commit format:
-<type>(<scope>): <summary>
+<!-- What does this PR do and why? (Features, fixes, or refactors) -->
 
-Examples:
-- feat(frontend): add event editor UI
-- fix(backend): correct field validation
-- docs(common): update contributing guide
-- chore(deps): update frontend packages
--->
+## 🛠️ Scope & Verification
 
-## ✨ What’s Changed?
+**Workspace:**
+- [ ] frontend  |  - [ ] backend  |  - [ ] common/config
 
-<!--
-Clearly describe what this PR does. Mention:
-- New features
-- Fixes
-- Refactors
-- Docs or config changes
--->
+**Checklist:**
+- [ ] Manually tested and verified locally
+- [ ] Automated suite passes cleanly (formatting, linting, tests)
+- [ ] New/updated unit tests included (if applicable)
 
-## 🧪 How to Test It
+## 📝 Developer Notes (Optional)
 
-<!--
-Explain how to manually test the change, or link to automated test coverage.
-If not testable, explain why.
--->
-
-## 📂 Scope
-
-<!-- Choose one or more folders this PR affects -->
-- [ ] frontend
-- [ ] backend
-- [ ] common/shared
-- [ ] CI/config
-
-## 📝 Notes (Optional)
-
-<!--
-Anything unusual, breaking, or helpful for reviewers.
--->
-
-## ✅ Checklist
-
-- [ ] PR title uses Conventional Commit format
-- [ ] Code is clean and commented where needed
-- [ ] I’ve manually tested relevant parts
-- [ ] I’ve updated docs (if needed)
+<!-- Breaking changes, architecture context, or specific areas for review -->

AI.md

@@ -8,12 +8,20 @@
 
 ## 🚦 Strict Workflow Protocol
 Before modifying, generating, or deleting any files, the agent MUST follow these steps in exact order:
+
 1. **Plan First:** Present a comprehensive architectural review, design summary, or pseudo-code strategy. Wait for explicit user greenlight.
 2. **Git Branching:** Checkout to a distinct feature or refactor branch from `main` using the Conventional Commits specification (e.g., `feat(backend)/...`, `refactor(frontend)/...`).
-3. **Execution:** Apply the changes within the tightly scoped workspace directory.
-4. **Finalize:** Upon user validation, stage and commit changes with concise, structured commit messages.
-5. **Documentation:** Auto-generate a pull request summary titled `pr_description.md` in the project root adhering to the workspace markdown template.
-
+3. **Execution:** Apply code modifications within the tightly scoped workspace directory.
+4. **Code Quality & Validation:** Before asking for user confirmation, you must ensure the code is clean and passes all local checks. Run the following commands based on the affected workspace:
+   - **If Backend changed:** Run `make format` followed by `make lint` inside the `/backend` directory.
+   - **If Frontend changed:** Run `npm run format` followed by `npm run lint` inside the `/frontend` directory.
+5. **Testing Suite Execution:** Run the test suite to ensure zero regressions. You must invoke tests in **non-interactive, run-once mode** so the process does not hang:
+   - **Backend:** Run `make test` from the `/backend` folder.
+   - **Frontend:** Run `npm run test:unit -- --run` (or the equivalent non-watching continuous integration command) from the `/frontend` folder.
+6. **Test Coverage Prompt:** Once checks pass, explicitly prompt the user: *"Would you like me to prepare or update any unit tests specific to these changes before we commit?"*
+7. **Finalize:** Upon user validation, stage and commit changes with concise, structured commit messages following the Conventional Commits format.
+8. **Documentation:** Auto-generate or update a pull request summary saving it directly to `pr_description.md` in the project root. The layout of this file must copy the formal structure defined in the repository's native GitHub file: `.github/PULL_REQUEST_TEMPLATE.md`.
+9. 
 ---
 
 ## 🐍 Backend Specifics (`/backend`)
@@ -28,4 +36,11 @@ Before modifying, generating, or deleting any files, the agent MUST follow these
 *Focus rules when operating within the frontend directory:*
 - **Framework Stack:** Vue 3 (Composition API, `<script setup>`), Vite, Tailwind CSS v4, and Shadcn-vue via `reka-ui`.
 - **State Management:** Server state must be tightly managed via TanStack Query (Vue Query). Pinia is strictly reserved for transient global application primitives like Authentication.
-- **Data Synchronization:** UI component tables must synchronize filtering, sorting, and pagination state unidirectionally using TanStack Table's native state updaters feeding directly into `vue-router` query parameters. Avoid redundant watchers or cyclical loop patterns.
+- **Data Synchronization:** UI component tables must synchronize filtering, sorting, and pagination state unidirectionally using TanStack Table's native state updaters feeding directly into `vue-router` query parameters. Avoid redundant watchers or cyclical loop patterns.
+
+---
+
+## 🏁 Completion Signal
+When every protocol step is completely finished, your final output to the user MUST explicitly print this statement on a standalone line for tracking visibility:
+
+🚀 **Success! Pull Request documentation has been successfully generated/updated in `pr_description.md`.**