tkmind/tkmind_go
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

added notes about reducing context window by referencing external files (#3895)

Browse Source
This commit is contained in:
w. ian douglas
2025-08-06 13:11:06 -06:00
committed by GitHub
parent 1bd4298e69
commit bb26521471
2 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/docs/guides/using-goosehints.md
+3 -1
View File
@@ -78,6 +78,8 @@ The `.goosehints` file can include any instructions or contextual details releva
A good time to consider adding a `.goosehints` file is when you find yourself repeating prompts, or providing the same kind of instructions multiple times. It's also a great way to provide a lot of context which might be better suited in a file.
Goosehints are loaded at the start of your session and become part of the system prompt sent with every request. This means the content of `.goosehints` contributes to token usage, so keeping it concise can save both cost and processing time.
## Setting up hints
The `.goosehints` file supports natural language.
@@ -124,4 +126,4 @@ Like prompts, this is not an extensive list to shape your `.goosehints` file. Yo
- **Keep file updated**: Regularly update the `.goosehints` file to reflect any changes in project protocols or priorities.
- **Be concise**: Make sure the content is straightforward and to the point, ensuring Goose can quickly parse and act on the information.
- **Start small**: Create a small set of clear, specific hints and gradually expand them based on your needs. This makes it easier to understand how Goose interprets and applies your instructions.
**Reference other files**: Point Goose to relevant files like /docs/style.md or /scripts/validation.js to reduce repetition and keep instructions lightweight.