Prompting Guide

Be clear and give context

• Say exactly what you want; repetition for clarity is fine.
  • Example: "Add a 1.5R stop loss to my EMA crossover strategy."
• Provide ample context; more detail beats too little.
  • Example: "Pine Script v5, 5m timeframe; use hl2; broker timezone NY."
• Expand acronyms on first use and define specialized terms.
  • Examples: "FVG → Fair Value Gap", "EMA → Exponential Moving Average".

Collaborate and plan first

• It's okay to brainstorm—plan with Horizon AI before coding.
  • Example: "Before coding, outline an approach to mean reversion entries."
• Ask how your code works first (e.g., pivot points) before changing it.
  • Example: "How are pivot points computed in this script?"
• Check whether a feature already exists before asking to add it.
  • Example: "Do we already have a take profit? If so, where is it set?"
• Keep one topic per thread and correct misunderstandings directly.
  • Example: "New thread: change stop loss to ATR-based (separate from indicator requests)."