|
|
@@ -7,13 +7,18 @@ Before any `git push` or claiming a task is "ready", the AI MUST:
|
|
|
3. **Production Build**: Run `npm run build` or `vite build` to ensure the project compiles correctly and there are no circular dependencies or missing imports in the production bundle.
|
|
|
4. **Local Verification**: If possible, verify the UI changes via screenshots or browser tools.
|
|
|
|
|
|
+5. Use cmd /c for Windows commands
|
|
|
+
|
|
|
## Search and Investigation
|
|
|
- **ALWAYS** use `python tools/search.py "query"` instead of `grep` or `ripgrep` for searching code.
|
|
|
- Example: `python tools/search.py "t(\"admin.tabs\"" --include .vue .ts`
|
|
|
- This ensures consistent results across different operating systems and avoids shell escaping issues.
|
|
|
|
|
|
+## Backend and Database
|
|
|
+- **ALWAYS** provide database migrations as `.sql` files in `backend/migrations/` (naming: `00X_name.sql`).
|
|
|
+- Avoid using one-off `.py` scripts for production migrations as they are not tracked by the automatic deployment script.
|
|
|
+
|
|
|
## Localization Rules
|
|
|
-- **NEVER** edit `en.admin.json`, `ru.json`, etc., directly.
|
|
|
- **NEVER** edit `translations.admin.json` or `translations.user.json` directly.
|
|
|
- **ALWAYS** edit fragments in `src/locales/master_admin/` or `src/locales/master_user/`.
|
|
|
- After editing fragments, run the `split` command to propagate changes.
|