So, based on how I used prompt-tower right now, where's what would make it more useful on the day to day.
I get a menu entry (and keybind) that opens a prompt creation tab.
In that creation tab, I have (order at your discretion)
- The file browser that lets me select files and folders to include in my prompt. Every file is added to the prompt in a format like content of file (most models understand structure of prompts better if they are structured as xml: https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/use-xml-tags )
- For each file selected, we look into its folder and the folders above it up to the root) for hidden instruction files like .cursor or .github-workspace.md files (there's like 5 or 6 different filename standards to look at used by different tools, but they all do the same thing, they are instructions about how to generate code related to that folder), and if a folder has that file we add that file to the list of files/contents of the tab. each of these instruction file we find we add to the prompt as the instructions
- There's also a text area to enter stuff manually. ( or something ).
I was about to add a section where you can specify documentation files and integrate them, but it's easy enough to implement that with the .cursor file stuff, no need for an extra feature I guess.
If I had this in my prompt-tower, it would speed things so much, most of what you read above (looking for instruction files, copy/pasting them into xml tags, etc) is stuff I do by hand right now.
As always, thanks so much.
So, based on how I used prompt-tower right now, where's what would make it more useful on the day to day.
I get a menu entry (and keybind) that opens a prompt creation tab.
In that creation tab, I have (order at your discretion)
I was about to add a section where you can specify documentation files and integrate them, but it's easy enough to implement that with the .cursor file stuff, no need for an extra feature I guess.
If I had this in my prompt-tower, it would speed things so much, most of what you read above (looking for instruction files, copy/pasting them into xml tags, etc) is stuff I do by hand right now.
As always, thanks so much.