Note: So far, this only covers some bits and pieces of the whole core.
DevAssistant has couple of load path entries, that are searched for assistants, snippets, icons and files used by assistants. In standard installations, there are three paths:
Each load path entry has this structure:
assistants/
crt/
mod/
prep/
files/
crt/
mod/
prep/
snippets/
icons/
crt/
mod/
prep/
snippets/
Icons under icons directory and files in files directory “copy” must the structure of assistants directory. E.g. for assistant assistants/crt/foo/bar.yaml, the icon must be icons/crt/foo/bar.svg and files must be placed under files/crt/foo/bar/
DevAssistant loads assistants from all load paths mentioned above (more specifically from <load_path>/assistants/ only), traversing them in order “system”, “local”, “user”.
When DevAssistant starts up, it loads all assistants from all these paths. It assumes, that Creator assistants are located under crt subdirectories the same applies to Modifier (mod) and Preparer (prep) assistants.
For example, loading process for Creator assistants looks like this: