Write good requests

• Where: the page and the part of it, like “the top of the home page” or “the price list on Services”. Or point at it, see below.
• What: the change itself, with the real content. Give the prices, the opening hours, the names. frascati never makes up facts: what it does not know appears as a [placeholder] in square brackets.
• How it should be afterwards: the result you want, not how to build it. “Calmer, with more space and one big photo” works better than “change the padding”.
• What stays: say it when something must not change, like “keep the photo” or “only the text, not the layout”.

One topic per message gives the best results. Several small things can go into one message as a list; large changes go better one after the other, so you can check each one in the preview.

Select

Click an element in the preview, like a heading, a button or a photo. Change with AI makes your next message about exactly that element, so “make this bigger” is enough. For a text, Edit text changes the words right in the preview, without credits.

Screenshot

Drag over a part of the preview and write what should change there. A message can hold several screenshots, each with its own note.

Images

Add your logo or your own photos with the image button, or paste them. Say where each one goes, like “this photo at the top of the home page”.

Dictate

The microphone in the chat box turns what you say into text. Handy for long descriptions.

For a new page, a new part like a shop or bookings, or a change across the whole website, choose Plan in the menu next to the chat's send button, where it says Build. frascati then changes nothing yet:

1. 1

   It asks what it needs to know. Pick an answer or write your own, then click Continue. Skip the questions makes the plan with sensible assumptions.

2. 2

   It shows a plan with its steps. Untick steps you do not want, or click Change the plan and say what should be different.

3. 3

   Build this plan carries it out, or only the steps still ticked.

Plan also answers questions about your website without touching it, like “What would you improve on the home page?”. A question uses 0.1 to 0.5 credits.

What should always hold goes into Instructions for the AI in the project menu (click the project's name at the top left), up to 4,000 characters. frascati follows them in every change, so you do not repeat them in each message.

• Say what is wrong and how it should be instead: “The heading is too long, at most five words” works better than “not like that”.
• Undo under the latest answer takes the change back, and Try again asks for it once more. Clearer wording often helps more than trying again.
• Versions in the project menu lists every build with what it changed. Restore brings back an earlier one, and the later versions stay.
• After each answer, frascati suggests next steps you can click. They are ideas, not a to-do list.
• If the preview shows an error, Fix it in the bar below the preview repairs it, free up to 10 times a day.

Most changes use less than 1 credit; a large change across many pages uses more. Typing a text with Edit text and fixing errors with Fix it use none. See Plans and credits.