From cf338e8f1db0c782b783f1a3bbe82ae2f80bbfe1 Mon Sep 17 00:00:00 2001 From: Bradley Axen Date: Sun, 5 Apr 2026 16:32:22 -0700 Subject: [PATCH] fix: resolve MDX compilation error in using-goosehints.md The numbered list containing
tags was broken by a paragraph inserted between items 1 and 2, causing MDX to fail with: 'Expected a closing tag for
before the end of paragraph' Move the note about nested hint persistence after the numbered list and wrap it in a :::note admonition. Also remove trailing whitespace on a
tag. Signed-off-by: Bradley Axen --- .../docs/guides/context-engineering/using-goosehints.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/documentation/docs/guides/context-engineering/using-goosehints.md b/documentation/docs/guides/context-engineering/using-goosehints.md index aeb08d5c43e7..cf53fb9b1df4 100644 --- a/documentation/docs/guides/context-engineering/using-goosehints.md +++ b/documentation/docs/guides/context-engineering/using-goosehints.md @@ -151,8 +151,6 @@ If you start goose in `my-project/`, the root-level hints are loaded immediately Use conventional commits for all changes. ```
- -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.
`frontend/.goosehints` ``` @@ -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. ``` -
+ 3.
`frontend/components/.goosehints` (current directory) ``` @@ -195,6 +193,10 @@ After nested hints are loaded for a directory, they remain active for the rest o ```
+:::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: