Write good prompts
Practical tips for getting better results from Hull's agents.
Hull does its best work when it knows what you want, where to look and how to tell it's done. These habits help.
Be specific
Say what to change, where, and what the result should be.
| Instead of | Try |
|---|---|
| Fix the button. | @src/components/Button.tsx The button stays disabled after the form becomes valid. Fix it so it enables as soon as all required fields are filled. |
| Write some tests. | Add unit tests for parseDate in src/utils/date.ts. Cover invalid input, time zones and leap years. Use the existing Vitest setup. |
| Make it faster. | The /search endpoint takes about 2 seconds. Find out why and propose a fix before changing anything. |
Point to the right context
Use mentions such as @path/to/file to bring files and folders into the conversation, instead of making Hull search for them. Paste error messages and stack traces in full.
Say how to check the work
Tell Hull how to know it's finished: "Run npm test and make sure it passes", or "The page should load without console errors." Hull can then verify its own work rather than stopping when the code looks right.
Plan before big changes
For larger tasks, start with the plan agent, or ask for a plan first:
- Ask Hull to look at the code and propose an approach.
- Read the plan and correct anything that's off.
- Switch to
codeand ask it to carry out the plan. - Review the changes as they come in.
Splitting a large task into smaller steps also makes each change easier to review.
Put repeated guidance in instructions
If you find yourself repeating the same guidance, such as "use pnpm" or "follow our error-handling pattern", put it in AGENTS.md or your instructions. For routines you run often, create a command or a skill.
Steer as you go
- If Hull heads the wrong way, stop it and explain what to do differently.
- When you reject an action, say why. Hull uses the reason to adjust.
- Use
/undoto roll back the last message and its changes, then try a clearer prompt. - If a conversation gets long and unfocused, start a new session with a short summary of where things stand.