Getting Started
Writing Effective Prompts
Practical patterns for describing trading bots, dashboards, and tools so you get production-ready results.
Last updated:
Write prompts that get results
The clearer your description, the closer the first build lands to what you want. Treat the prompt like a spec for your bot or dashboard: state what it is, the market it trades, the rules it follows, and the interface you want to see.
Patterns that work
- Name the pair and strategy.“DCA bot that buys $50 of ETH daily and tracks average cost” beats “a trading bot”.
- State the rules precisely. Entry and exit conditions, grid levels and spacing, take-profit, stop-loss, and the schedule the bot runs on.
- Describe the interface.Say what panels or charts you want — open positions, realized and unrealized P&L, allocation, a live price or signal feed.
- Iterate. Ship a first version, then refine it in chat one change at a time.
Vague versus specific
A vague prompt leaves the important decisions to chance. Compare:
Vague
“Make me a trading bot.”
Specific
“A grid bot for ETH/USDT with 10 grid levels between $2,000 and $3,000, 0.5% take-profit per level, and a dashboard showing open orders, filled orders, and total realized P&L. Start in paper mode.”
Things to avoid
Avoid vague, do-everything prompts. Build one focused project, get it working, then expand. Cryptohopper.AI generates code with AI, so you are responsible for reviewing and testing what you build — and for running it in paper mode — before connecting it to real funds.