The current process suggests that users install the unity-editor skill and replace it when they update unityctl. This works well enough for the tool itself, but there is not a clear way for users to add project specific details that are relevant when using unityctl.
The solution here could be suggesting that users store any extra stuff in a different skill or a claude.md file. It could also be some sort of system for updating the main skill without overwriting changes. We could have the skill @ refer to a file where users would add their details and would be empty by default, or some more elegant solution.
The current process suggests that users install the unity-editor skill and replace it when they update unityctl. This works well enough for the tool itself, but there is not a clear way for users to add project specific details that are relevant when using unityctl.
The solution here could be suggesting that users store any extra stuff in a different skill or a claude.md file. It could also be some sort of system for updating the main skill without overwriting changes. We could have the skill @ refer to a file where users would add their details and would be empty by default, or some more elegant solution.