Writing good prompts

Principles

• Be specific. “Add a contact form with name, email and message, sending to my email” beats “add contact”.
• One goal per message. Large changes split into steps are more reliable.
• Describe the outcome, not the code. Say what users should see and do.
• Show, don't tell. Attach a screenshot or a reference image of a style you like.
• Name the place. “On the pricing page, in the second card…”.

When something is wrong

1. 1Describe what you expected and what actually happens.
2. 2Mention the page and the action (“after clicking Book now…”).
3. 3Attach a screenshot if it is visual.
4. 4If a change made things worse, restore the previous version and try a different wording.

Knowledge

Rules you want Master to follow in every project — brand tone, colors, preferred language — belong in Knowledge so you don't have to repeat them.