docs: enforce correct Vuexy reference path in CLAUDE.md and .cursorrules

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.cursorrules

@@ -9,6 +9,11 @@ PHP 8.2 + Laravel 12 | TypeScript + Vue 3 + Vuexy/Vuetify | Pinia + TanStack Que
 - Global scope `OrganisationScope` on event-related models
 - Policies for authorization — never inline role checks
 
+## Vuexy reference path (mandatory)
+- When looking at Vuexy examples, demos, or patterns, ALWAYS reference:
+  `resources/vuexy-admin-v10.11.1/vue-version/typescript-version/full-version/`
+- Never reference `javascript-version/` or `starter-kit/` variants
+
 ## Vue 3
 - `<script setup lang="ts">` always
 - TanStack Query for API state, Pinia for UI state

CLAUDE.md

@@ -77,6 +77,25 @@ Configure two frontend origins in both Laravel (`config/cors.php` via env) and t
 
 ## Frontend rules (strict)
 
+### Vuexy reference source (mandatory)
+
+When referencing Vuexy demo pages, components, or patterns, ALWAYS use the TypeScript Vue version at:
+
+```
+resources/vuexy-admin-v10.11.1/vue-version/typescript-version/full-version/
+```
+
+This is the **ONLY** valid reference path. Never use:
+- `javascript-version/` — wrong language
+- `starter-kit/` — incomplete, missing components
+- Any other variant or version
+
+Before implementing any Vuexy-based page or component, read the reference implementation from this path first:
+```bash
+# Example: find auth page references
+find resources/vuexy-admin-v10.11.1/vue-version/typescript-version/full-version/src/pages -name "*.vue" | grep -i "login\|auth"
+```
+
 ### Vuexy-first strategy
 
 Before writing ANY frontend component, consult `/dev-docs/VUEXY_COMPONENTS.md` and follow this decision tree: