docs: Adding a .goosehints guide (#279)
Co-authored-by: Angie Jones <jones.angie@gmail.com>
This commit is contained in:
@@ -17,7 +17,7 @@ default:
|
||||
requires: {}
|
||||
```
|
||||
|
||||
### Fields
|
||||
### Fields
|
||||
|
||||
#### provider
|
||||
|
||||
@@ -104,6 +104,7 @@ unit-test-gen:
|
||||
```
|
||||
|
||||
[jinja-guide]: https://jinja.palletsprojects.com/en/3.1.x/
|
||||
[using-goosehints]: https://block.github.com/goose/guidance/using-goosehints.html
|
||||
|
||||
|
||||
## Adding a toolkit
|
||||
@@ -145,5 +146,7 @@ Goose ships with the ability to read in the contents of a file named `.goosehint
|
||||
|
||||
This file will be read into the Goose system prompt if it is present in the current working directory.
|
||||
|
||||
> [!NOTE]
|
||||
Check out the [guide on using .goosehints][using-goosehints] for more tips.
|
||||
|
||||
> [!NOTE]
|
||||
> `.goosehints` follows [jinja templating rules][jinja-guide] in case you want to leverage templating to insert file contents or variables.
|
||||
Reference in New Issue
Block a user