How-to · · goose · 3 steps
goose .goosehints: Set project rules in 3 steps
Typing the same instructions to goose again and again?
Put them in a .goosehints file once and goose picks them up every session.
You need: goose with the Developer extension enabled.
Steps
- Create a file named
.goosehints: in~/.for rules that apply to every session, or at the root of your project for that project only.config/ goose - Write your rules as clear, direct sentences, most important first, such as
Run unit tests before committing any changes.Add@README.mdto pull a file’s content in. - Restart your goose session so it reads the file.
Heads-up
- goose loads hints when a session starts, so edits show up after a restart.
- When your project hints and global hints conflict, the project hints win.
- Hints ride along with every request and use tokens, so keep them short.