awesome-bookmarks/goose
3
0
Fork 0
mirror of https://github.com/block/goose.git synced 2026-07-17 12:56:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix: resolve MDX compilation error in using-goosehints.md (#8332)

Browse Source 
Signed-off-by: Bradley Axen <baxen@squareup.com>
This commit is contained in:
Bradley Axen
2026-04-05 16:39:40 -07:00
committed by GitHub
parent e94f304780
commit 85f513d55f
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/docs/guides/context-engineering/using-goosehints.md
+5 -3
View File
@@ -151,8 +151,6 @@ If you start goose in `my-project/`, the root-level hints are loaded immediately
Use conventional commits for all changes.
```
</details>
After nested hints are loaded for a directory, they remain active for the rest of the session. If you update a hint file and want goose to pick up the new content reliably, restart the session.
2. <details>
<summary>`frontend/.goosehints`</summary>
```
@@ -179,7 +177,7 @@ After nested hints are loaded for a directory, they remain active for the rest o
Always confirm UI changes with design team before implementation.
```
</details>
</details>
3. <details>
<summary>`frontend/components/.goosehints` (current directory)</summary>
```
@@ -195,6 +193,10 @@ After nested hints are loaded for a directory, they remain active for the rest o
```
</details>
:::note
After nested hints are loaded for a directory, they remain active for the rest of the session. If you update a hint file and want goose to pick up the new content reliably, restart the session.
:::
## Common Use Cases
Here are some ways people have used hints to provide additional context to goose: