A common migration path will be people having ai dev kit already installed, using this new install.
We should sync with ai dev kit and find a way to:
- give instructions to cleanup the legacy ai dev kit mcp server so that it doesn't conflict/polute the prompt
- detect ai dev kit skills that have been removed/duplicated and offer to remove them too
- The same logic should be shared with ai dev kit once the adk installer loads DAS directly
- this might differ if adk was installed at the folder level or global level (in this case we should offer to install DAS at the global level too if the MCP is global, so that other projects also migrate)
I'm not sure where this should be implemented, should we have a hook calling a script in ai dev kit scanning for previous install during the install? @jamesbroadhead any recommendations?
A common migration path will be people having ai dev kit already installed, using this new install.
We should sync with ai dev kit and find a way to:
I'm not sure where this should be implemented, should we have a hook calling a script in ai dev kit scanning for previous install during the install? @jamesbroadhead any recommendations?