Enhance Custom Instructions for All Mode: Enable File Editing and Version Control

[devxpain]

Currently, I find managing "Custom Instructions for All Modes" through the existing UI to be a significant pain point. Updating these instructions is cumbersome, and I lack the ability to easily version control them. This makes it difficult for me to track changes, collaborate, or revert to previous versions of my custom instructions.

I propose an elegant and simple solution: migrating the storage of custom instructions from the current UI-driven mechanism to a dedicated file, such as a Markdown file. This shift would give me a more flexible and robust way to manage my custom instructions.

My primary goals for this feature are to:

• Enable External Editing: I want to be able to edit my custom instructions directly in a file using my preferred editor, which would provide a more familiar and efficient workflow.
• Facilitate Version Control: I need to integrate my custom instructions into standard version control systems (like Git), allowing me to track changes, collaborate with others, and easily roll back to previous versions.
• Improve My Experience: I want a streamlined process for updating and refreshing my custom instructions, ensuring that any changes I make externally are quickly reflected within the application.

By adopting a file-based approach, I believe we can significantly enhance the usability and maintainability of custom instructions, directly addressing the current pain points I experience and providing a more powerful management solution.