From 72120969c602f595f87f77b2cec5ab234f4b517c Mon Sep 17 00:00:00 2001 From: "bert.hausmans" Date: Tue, 14 Apr 2026 01:27:44 +0200 Subject: [PATCH] docs: add Vuexy-first strategy and frontend conventions to CLAUDE.md Co-Authored-By: Claude Opus 4.6 (1M context) --- CLAUDE.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 837d01e0..f679d0be 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -80,6 +80,36 @@ Configure three frontend origins in both Laravel (`config/cors.php` via env) and ## Frontend rules (strict) +### Vuexy-first strategy + +Before writing ANY frontend component, consult `/dev-docs/VUEXY_COMPONENTS.md` and follow this decision tree: + +1. **Can a standard Vuetify component do this?** → Use it with default props. + Do not wrap it in a custom component. +2. **Does Vuexy provide an @core component for this?** → Use it. Check + `/dev-docs/VUEXY_COMPONENTS.md` section 1 for the full registry. +3. **Does an existing Crewli page already solve a similar UI pattern?** → + Copy that pattern exactly. Check `/dev-docs/VUEXY_COMPONENTS.md` section 3 + for established patterns and their reference implementations. +4. **None of the above?** → Only then write custom code. Add `