How to ask

You do not have to write well for Setherion to build something. You do have to be clear about what you want, and clearer still about what you want changed.

Everything below is a habit worth having, not a rule. Nothing here is required, and a plain sentence works.

Say what it is and who it is for

The first sentence decides what gets built. It is read for three things: what kind of thing this is, what it is about, and what it must have.

The line above the box, with Website, Web App, Mobile App, Landing Page, 3D Game and SaaS, does the same job in one press. Use it when your sentence could mean two of them. "A website for a medical centre" can be a site for its patients or the screen its staff work in, and that mark settles it.

Name the parts you want

An app is easier to ask for as a list of parts than as an idea. Everything you name gets built. Everything you leave out is guessed at, and the guess is usually reasonable, but it is still a guess.

A landing page for a coffee shop, with the menu, the opening hours,
photos of the place, a map, and a form for table reservations

You do not need to describe how each part looks. "A gallery" is enough; "a gallery with three columns on a computer and one on a phone" is what already happens.

Change one thing at a time

A change is understood against the app as it is now, so it can be short. "Make the header dark" is a whole request.

Several unrelated changes in one message are harder to get right than the same changes sent one after the other, and when something comes out wrong you cannot tell which part caused it. Send them separately.

Instead of one message carrying everything:

Make the header dark, add a reservation button, change the font,
add a gallery and translate it into German

send three, and look at the app between them:

Make the header dark
Add a Reserve a table button in the header
Add a photo gallery under the menu

Point at what you mean

Words like "that button" mean nothing on their own, and there is a faster way than describing where it sits.

• Edit in the preview: click a word or a picture and change it directly, no request needed.
• The box above the preview names the section you are looking at, and takes you to any other. A section name in your request tells you are talking about that part.
• In the code, select a few lines and send them with your message. They arrive attached to it, so "this does the wrong thing when the list is empty" is enough.
• With the code beside the preview (Split view), switch on the pointer and click anything in the preview: the file opens at the line that makes it, ready to attach. See Code.
• On a picture in the Code view, Draw marks it in red to show what you mean, and Add to chat sends it with your next message.

Show what you mean

The + next to the box takes a picture or a document, and more.

• Upload a file. A screenshot or a photo of a design: the app gets built to look like it. A menu, a price list, a catalogue as a PDF, Word, text, Markdown, CSV or JSON file: what is inside it ends up in the app, instead of made up. Click the thumbnail afterwards to see what the builder made of it.
• Import from Figma, for a design you already have: the app is built from one of its frames. Import from Canva brings the pages of a design in as images to place in the app.
• Import an app made somewhere else, from Lovable, Bolt, v0, Base44, GitHub, a ZIP or a spreadsheet: Setherion builds it again here. This one is on the dashboard. See Import an app.
• Connectors: the services this app may use, like payments or email. Skills: things to build into it, like sign-in or bookings. See Connectors and Skills.
• Connect your repo, under GitHub project on the dashboard: sign in to GitHub once, then push the code from the editor, on a paid plan.

In the editor the menu is a little different: Upload file, Media AI (an image or a video, made and placed in the app: see Media and design tools), Design (Figma and Canva), Connectors and Skills.

Say it instead of typing

The microphone beside the Build button takes what you say. Your words appear in the box as you speak, and you press it again to stop. Read it over, change it if you like, and send. It works in the browser's own language. See Build, Chat and Plan.

Showing is usually faster than describing an appearance in words, and it is the only way to get your own content into the first build.

Write in your own language

Write the way you speak. Setherion reads which language your request is in, and the app comes out in that language: its buttons, its headings, the words on its pages.

Romanian, English, Spanish, French, German, Italian, Portuguese, Dutch, Polish, and anything written in Chinese, Japanese, Korean, Russian, Arabic, Hebrew or Greek letters are all recognised. If you want an app in a different language from the one you are writing in, say so: "in English" at the end of the request is enough.

Rules the app always follows

Some things you should not have to repeat. In the editor, AI Controls is at the foot of the model list: press the model button next to the box, the one that says Auto. It holds two of them:

• Custom instructions: rules followed on every build and every change of this app. "Keep the dark theme", "never use orange", "all prices in pounds", "write the text formally".
• Freeze Files: files nothing is allowed to touch. Freeze the page you have got exactly right, and the next change cannot undo it.

See AI Controls for both.

When you are not sure what you want

Two modes are there for exactly that.

• Plan, behind the Build button on the dashboard and in the editor, asks you a few quick questions and shows you a map of the app before it writes a single file. Worth it for anything you have not thought all the way through. Alt+P switches to the next mode without opening the menu.
• Chat, in the editor, talks about the app and never touches your code. Ask "what would you add to this page?" or "why is the form at the bottom?" and nothing happens to the app.

When something comes out wrong

Say what is wrong, not that it is wrong. "The form does not send" is a report; "the form says it sent but nothing arrives" is something that can be fixed.

If a change made things worse, say that too. "Put the menu back the way it was before that change" is understood.