How to write an effective build prompt
Structure your prompts so Getyn builds closer to what you want, faster.
A good prompt is specific about what to build and how it should look. Vague prompts lead to generic results.
A simple prompt formula
Build a [page/app type] for [who/what]. Include [sections/features]. Use a [style] look with [accent].
Do
- Name the sections or features you want ("hero, pricing, FAQ, contact form").
- Describe the style ("minimal", "premium", "playful") and any brand colors.
- Give real context — the product name, audience, and tone.
- Build one coherent thing per prompt, then iterate.
Avoid
- One-word prompts like "make a website".
- Asking for many unrelated features in a single message.
- Assuming Getyn knows private details — include them.
Important
If a request is very large (a full multi-feature system), Getyn may suggest building it in phases. Approving the plan builds it one usable piece at a time, which is more reliable than trying to do everything at once.
Example
Build a portfolio site for a freelance photographer named Mia. Include a full-bleed hero with a background image, a masonry gallery, an about section, a services list with prices, and a contact form. Elegant, editorial style with lots of whitespace and a warm neutral palette.
Next
Was this article helpful?