chore: Refactor project standards and documentation

- Removed the obsolete `.cursorrules` file to streamline project structure.
- Updated various documentation files to emphasize the importance of reading `ai_docs/` for project standards.
- Clarified references to backend and frontend standards, ensuring consistency across all relevant documents.
- Enhanced the `AI_TOOLING_STANDARDS.md` with a comprehensive index of all related documents for better accessibility.

Author: Tendo33

.agents/rules/project-development.md

@@ -2,11 +2,11 @@
 trigger: always_on
 ---
 
-Follow `ai_docs/AI_TOOLING_STANDARDS.md` as the default engineering contract.
+**Read `ai_docs/` for project standards.** `ai_docs/AI_TOOLING_STANDARDS.md` has the full docs index.
 
 - Plan before implementation and keep edits minimal.
-- Prefer Python 3.10+ + uv + ruff + pytest for backend tasks.
-- For backend API/service design, follow `ai_docs/BACKEND_STANDARDS.md`.
+- Backend rules: `ai_docs/BACKEND_STANDARDS.md`.
+- Frontend rules: `ai_docs/FRONTEND_STANDARDS.md`.
+- Scripts (rename/version): `ai_docs/SCRIPTS_GUIDE.md`.
 - Use explicit typing and predictable error handling.
 - Do not claim completion without relevant verification commands.
-- Frontend stack: pnpm + React + TypeScript + Vite + Tailwind CSS + shadcn/ui.

.agents/skills/project-development-playbook/SKILL.md

@@ -8,6 +8,8 @@ description: Use when implementing project tasks that need consistent coding sta
 
 Apply one consistent delivery workflow across backend and frontend tasks.
 
+**Reference:** Read `ai_docs/AI_TOOLING_STANDARDS.md` for the full docs index before starting.
+
 ## Workflow
 
 1. Confirm scope and assumptions.

.claude/skills/project-development-playbook/SKILL.md

@@ -8,6 +8,8 @@ description: Use when implementing project tasks that need consistent coding sta
 
 Apply one consistent delivery workflow across backend and frontend tasks.
 
+**Reference:** Read `ai_docs/AI_TOOLING_STANDARDS.md` for the full docs index before starting.
+
 ## Workflow
 
 1. Confirm scope and assumptions.

.codex/skills/project-development-playbook/SKILL.md

@@ -8,6 +8,8 @@ description: Use when implementing project tasks that need consistent coding sta
 
 Apply one consistent delivery workflow across backend and frontend tasks.
 
+**Reference:** Read `ai_docs/AI_TOOLING_STANDARDS.md` for the full docs index before starting.
+
 ## Workflow
 
 1. Confirm scope and assumptions.

.cursor/rules/backend-python-service-standards.mdc

@@ -2,7 +2,7 @@
 description: Backend service/API standards for Python projects using typed models, clear layering, and reliable verification.
 globs: src/**/*.py, tests/**/*.py
 ---
-- For backend API/service work, follow `ai_docs/BACKEND_STANDARDS.md`.
+- For backend API/service work, follow `ai_docs/BACKEND_STANDARDS.md`. See `ai_docs/AI_TOOLING_STANDARDS.md` for full docs index.
 - Use layered boundaries: API -> service -> repository -> domain.
 - Keep route handlers thin; place business logic in service layer.
 - Use Pydantic v2 models for request/response and validation.

.cursor/rules/frontend-react-typescript-vite-tailwind.mdc

@@ -2,6 +2,7 @@
 description: Default frontend stack and implementation standards for this project.
 globs: frontend/**/*.{html,css,js,jsx,ts,tsx,json}
 ---
+- **Follow `ai_docs/FRONTEND_STANDARDS.md` for full frontend conventions.**
 - Fixed stack: **pnpm** + React + TypeScript + Vite + Tailwind CSS + **shadcn/ui**.
 - Use shadcn/ui as the component library; customise via Tailwind and CSS variables.
 - Build reusable UI primitives in `frontend/src/components/ui`.

.cursor/rules/project-development-standards.mdc

@@ -2,9 +2,11 @@
 description: Project-wide engineering contract across backend and frontend work.
 globs: **/*
 ---
-- Follow `ai_docs/AI_TOOLING_STANDARDS.md` for workflow and quality gates.
-- Follow `ai_docs/BACKEND_STANDARDS.md` when implementing backend API/service behavior.
+- **Read `ai_docs/` for project standards.** `ai_docs/AI_TOOLING_STANDARDS.md` has the full index.
+- Backend: `ai_docs/BACKEND_STANDARDS.md`. Frontend: `ai_docs/FRONTEND_STANDARDS.md`.
+- Scripts (rename/version): `ai_docs/SCRIPTS_GUIDE.md`.
 - Plan first, implement minimal changes, and verify before completion.
 - Backend default: Python 3.10+, uv, ruff, pytest.
+- Frontend default: pnpm + React + TypeScript + Vite + Tailwind CSS + shadcn/ui.
 - Keep functions typed, explicit, and testable.
 - Handle failures explicitly; avoid silent exception swallowing.

.cursor/skills/project-development-playbook/SKILL.md

@@ -2,6 +2,8 @@
 
 Apply one consistent delivery workflow across backend and frontend tasks.
 
+**Reference:** Read `ai_docs/AI_TOOLING_STANDARDS.md` for the full docs index before starting.
+
 ## Workflow
 
 1. Confirm scope and assumptions.

.cursorrules

@@ -11,9 +11,11 @@ Use this file as the default project contract for Codex.
 
 ## Engineering Rules
 
-- Follow `ai_docs/AI_TOOLING_STANDARDS.md`.
-- Follow `ai_docs/BACKEND_STANDARDS.md` for backend API/service tasks.
-- Prefer Python 3.10+ + uv + ruff + pytest for backend work.
+- **Read `ai_docs/` for project standards before starting work.**
+- Core contract: `ai_docs/AI_TOOLING_STANDARDS.md` (contains full index of all docs).
+- Backend rules: `ai_docs/BACKEND_STANDARDS.md`.
+- Frontend rules: `ai_docs/FRONTEND_STANDARDS.md`.
+- Scripts (rename/version): `ai_docs/SCRIPTS_GUIDE.md`.
 - Keep functions small, typed, and testable.
 - Handle errors explicitly; avoid silent failures.