Prompting best practices

Be specific

Vague prompts produce vague results. Instead of "make a nice website", describe exactly what you want:

Build a landing page for a freelance designer.
- Hero with full-width gradient background and headline "Design that works"
- Services section with 3 cards (UX, UI, Branding)
- Testimonials slider with 3 quotes
- Contact form with name, email, and message
- Dark theme, Inter font, purple accent (#7C3AED)

One change at a time

Large multi-step prompts can be harder to control. For big features, build the foundation first, then refine. Small, focused prompts are easier to review and fix.

Describe style and mood

Always include the visual direction: minimalist, playful, corporate, dark mode, light mode, typography, color palette, spacing, and animation preferences. If you have a reference image, upload it.

Use references

Screenshots, URLs, and competitor examples are excellent inputs. Master can read images and imitate layouts, colors, and typography. Paste a link and say "use this style".

Iterate in small steps

After each generation, review the preview and ask for precise adjustments. Good follow-up prompts look like:

• "Increase the hero padding by 40px."
• "Make the cards 2 columns on desktop and 1 on mobile."
• "Change the button color to #F97316."
• "Add a subtle hover animation to the navbar links."

Example prompts

Landing page

Build a SaaS landing page for a time-tracking app called Clockwise.
- Hero with headline, subheadline, and CTA button
- Feature grid with 4 icons
- Pricing section with 3 tiers
- Footer with newsletter form
- Clean, modern, blue accent

Internal tool

Build an internal dashboard for approving vacation requests.
- Table with columns: employee, dates, status, actions
- Approve / reject buttons
- Filter by status and team
- Login required