Getting started
Prompting tips for non-coders
How to describe an AI worker so it comes out the way you wanted. Spoiler: short and specific beats long and fancy.
Rule 1 — Say what you want, not how to do it
Bad: “Use a transformer to analyze my tickets.” Good: “Read each support ticket and tell me what's wrong in one sentence.”
Rule 2 — Mention how often
“Every Monday morning” is way more useful than no schedule. We use it to decide if your worker should be a slash command, a hook, or a one-off.
Rule 3 — Mention who reads the answer
“For me only” → casual tone. “For our customers” → polite. “For our CEO” → terse and professional.
Rule 4 — Mention the shape of the answer
“3 bullets and a CTA”, “a one-paragraph summary”, “a punch list of fixes”. Saying the shape gets you the shape.
HEADS UP · Don't worry about being a good writer
Even a messy sentence works. We'll ask you tiny follow-up questions to fill in the gaps.