Client → Vault Path Mapping (canonical)
Purpose: Single source of truth for client name → knowledge/clients/ folder path. Skills and commands that read or write under knowledge/clients/ should use this mapping and the exact folder names (casing) so behavior is consistent on case-sensitive systems.
Convention: Folder names under knowledge/clients/ are lowercase unless an existing folder uses different casing (e.g. list knowledge/clients/ to confirm before creating new clients).
Mapping
| User says / client | Vault path | Linear team (if used) |
|---|---|---|
| LMNT | knowledge/clients/lmnt/ | LMNT |
| CTA | knowledge/clients/cta/ | CTA |
| ABC, ABC Home and Commercial | knowledge/clients/abchomeandcommercial/ | ABC Home and Commercial |
| Eden | knowledge/clients/eden/ | Eden |
| Hedra | knowledge/clients/hedra/ | Hedra |
| Honey Stinger / HoneyStinger | knowledge/clients/honeystinger/ | — |
| Insomnia Cookies | knowledge/clients/insomniacookies/ | — |
| MoEngage | knowledge/clients/moengage/ | — |
| Rimo | knowledge/clients/rimo/ | — |
| Urban Stems / UrbanStems | knowledge/clients/urbanstems/ | — |
| Readme | knowledge/clients/readme/ | — |
| Magic Spoon / MagicSpoon | knowledge/clients/magicspoon/ | — |
Other clients: List knowledge/clients/ and use the folder that matches the client (exact casing as on disk). When adding a new client, see “Adding a new client” below.
Adding a new client
- Create the folder under
knowledge/clients/using the intended folder name (lowercase recommended for consistency): e.g.knowledge/clients/newclient/. - Add a row to the table above (and to any command that has its own client table, e.g. weekly-kick-off-update).
- If the client has a Linear team, note it in the Linear team column so skills that use Linear MCP can resolve the team.
Reference: knowledge/clients/README.md for folder structure and classification rules.