Keep file work under Externa/**; do not call move_agent_to_root for sidebar/folder placement.
php artisan boost:add-skill qiick/externa-core
Save this content to: .cursor/rules/stay-in-externa-workspace.mdc
# Stay in the Externa workspace
This chat belongs to the **Externa** product workspace under:
`/Users/lucagiardi/Projects/LucaGiardi/Qiick/Externa/`
That parent folder holds sibling projects. It is **not** a single git repo.
## Default: leave the agent root alone
- Do **not** call `move_agent_to_root` (or `move_agent_to_cloned_root`) unless the user **explicitly** asks to change workspace roots for coding access.
- Never use `move_agent_to_root` to “put chat in Externa folder” / fix Agents sidebar grouping. That creates glass multi-root workspaces (auto names like `externa-core-externa-docs-and-4-more`) and **removes chats from custom Agents folders**.
- If already in a usable multi-root workspace or `externa-core` (or another `externa-*` sibling) with file access, **leave the root alone**.
- Stay under `Externa/**` for file work by using absolute paths / existing roots — **without** relocating the agent root.
## Forbidden
- **NEVER** call `move_agent_to_root` to leave `/Users/lucagiardi/Projects/LucaGiardi/Qiick/Externa/**`.
- **NEVER** use the parent folder alone as `rootPath`:
`/Users/lucagiardi/Projects/LucaGiardi/Qiick/Externa`
Cursor tries git checkout / branch migrate on that path. It is **not a git repository**, so attach fails with `fatal: not a git repository`.
- **NEVER** call `move_agent_to_root` for sidebar placement, folder restore, or “preferred multi-root attach” on product chats.
## When the user explicitly asks to change roots
Only then may you switch roots — and only to git repos under `Externa/**` (single `externa-*` or multi-root `rootPaths` of those siblings). Still never the parent `Externa` folder alone.
## If root drifts outside Externa/**
Do **not** auto-migrate with `move_agent_to_root`. Tell the user the chat left `Externa/**` and ask whether they want a root change. Prefer continuing with path-scoped file tools if access still works.
This chat belongs to the Externa product workspace under:
/Users/lucagiardi/Projects/LucaGiardi/Qiick/Externa/
That parent folder holds sibling projects. It is not a single git repo.
move_agent_to_root (or move_agent_to_cloned_root) unless the user explicitly asks to change workspace roots for coding access.move_agent_to_root to “put chat in Externa folder” / fix Agents sidebar grouping. That creates glass multi-root workspaces (auto names like externa-core-externa-docs-and-4-more) and removes chats from custom Agents folders.externa-core (or another externa-* sibling) with file access, leave the root alone.Externa/** for file work by using absolute paths / existing roots — without relocating the agent root.NEVER call move_agent_to_root to leave /Users/lucagiardi/Projects/LucaGiardi/Qiick/Externa/**.
NEVER use the parent folder alone as rootPath:
/Users/lucagiardi/Projects/LucaGiardi/Qiick/Externa
Cursor tries git checkout / branch migrate on that path. It is not a git repository, so attach fails with fatal: not a git repository.
NEVER call move_agent_to_root for sidebar placement, folder restore, or “preferred multi-root attach” on product chats.
Only then may you switch roots — and only to git repos under Externa/** (single externa-* or multi-root rootPaths of those siblings). Still never the parent Externa folder alone.
Do not auto-migrate with move_agent_to_root. Tell the user the chat left Externa/** and ask whether they want a root change. Prefer continuing with path-scoped file tools if access still works.
How can I help you explore Laravel packages today?