Writing good prompts

A Mythos prompt is a brief, not a spec. You describe the site you want in plain language and the builder turns it into a real React + Vite page. The clearer the brief, the closer the first build lands — and the fewer follow-up edits you spend credits on. This page is about getting that first build right.

Cost: a new project costs 3 credits; each edit costs 2. New accounts start with 5 free credits. A sharper prompt means fewer edits, which means fewer credits — see Credits & pricing.

Why prompt carefully

The builder writes real, industry-specific copy and picks a palette, fonts, and section layout from your words. If you leave those open, it decides for you. Naming what you care about up front means you spend your first 3 credits on a result you can ship or lightly tweak, instead of three rounds of “make it darker, change the font, add a pricing section.”

What to put in a prompt

The builder responds to four things. Cover the ones you care about; let it decide the rest.

Say this	Example	Why it helps
The kind of site + industry	”a landing page for a dental clinic”	The builder writes real copy for that industry, not lorem ipsum
The sections	”hero, services, pricing, testimonials, FAQ, footer”	Each becomes its own component; naming them sets the page structure
The tone / look	”clean and minimal” / “dark and industrial”	Drives the palette, fonts, and layout density
Any form that saves data	”a quote-request form that stores submissions”	Tells the builder you need a real backend (see below)

Name the sections in the order you want them down the page (“hero, then services, then pricing…”). The builder renders them top-to-bottom in roughly the order you list.

Example prompts

A vague prompt and a good prompt for the same idea:

Make me a website for my moving company.

Create a landing page for a moving company called Iron Anchor.
Sections: hero, services, pricing, testimonials, a quote-request form, and a footer.
Dark, industrial tone — heavy type, lots of contrast.

A few more that work well because they name the industry, the sections, and the tone:

A portfolio site for a freelance photographer.
Hero with a full-bleed image, an about section, a gallery grid, and a contact section.
Calm, editorial, lots of whitespace.

A landing page for a SaaS tool that schedules social posts.
Hero with a headline and CTA, a features grid, how-it-works, pricing with three tiers,
testimonials, FAQ, and a footer. Bright and modern, blue accent.

A one-page site for a neighborhood coffee shop.
Hero, our story, the menu, opening hours, and a map placeholder with the address.
Warm and cozy, cream and brown palette.

If a form must save data

By default the builder makes forms that look real but don’t store anything — they validate and show a success message. That’s fine for a marketing page. If you actually need submissions saved (a booking, a waitlist, a contact form you’ll read later), that needs a backend, and Mythos builds the frontend only.

Mythos builds the frontend; data lives in your own Supabase. To make a form store real submissions, connect your own Supabase project under More → Cloud. Once it’s connected, the builder wires the form to a real table in your database — including row-level security on every new table.

So there are two paths:

Just a marketing page? Don’t mention saving data — the builder makes a clean, working-looking form and you’re done.
Need the data? Ask for it directly. If Supabase is not connected, the same build pauses and opens Cloud. Connect an existing project or create one, and the build continues automatically with the original prompt and credit reservation.

Add a waitlist form to the hero — name and email — and save each
submission to my database.

If Supabase is not connected, Mythos stops before changing code and asks you to connect it. It does not fake persistence with browser-only state or replace the request with a frontend-only form.

One page at a time

A first prompt should describe one page, well. A multi-page site is several times the work, and the builder defaults to a single landing page unless you explicitly ask for more routes. Build the main page first, then add pages by chat:

Add an "About" page with the team and our history, linked from the nav.

How Plan mode helps

If you’d rather shape the build before writing code, turn on Plan mode next to the send button. Instead of building straight from your prompt, Mythos asks focused questions and saves an editable plan draft. Each accepted AI turn costs 1 credit after its response is saved; the Build after approval is charged separately.

Turn on Plan mode

Toggle Plan mode next to the send button, then send your prompt as usual.

Answer focused questions

Mythos asks only for missing product, content, interaction, data, or constraint details.

Review the editable draft

Mythos saves a durable plan draft. Edit and save its Markdown locally without making another AI call.

Approve the plan

Approve the exact draft to start the normal, separately charged Build.

Build mode vs Plan mode. Build mode builds directly from your prompt — fastest. Plan mode questions → editable plan draft → approval first, so you can settle the scope before any code exists. See Plan mode.

Plan mode is useful when requirements are still unclear or the first build needs an explicit scope. A concrete starting prompt makes its questions more relevant and its plan draft more precise.

Good to know

The builder picks what you don’t. Colours, exact layout, and section copy are decided for you unless you name them. You don’t have to specify everything — only what you care about.
Real copy, real industry. Mention the industry and the builder writes specific copy for it. Skip it and the copy is more generic.
Stock photos are used sparingly. The builder adds a few photos where they help (a hero, one gallery), not one per section — asking for “an image in every section” works against a clean result.
You’re not locked in. Anything the first build gets wrong is an edit away. See Fixing a build that isn’t right.

FAQ

How detailed should my first prompt be?

Detailed enough to name the kind of site, the industry, the sections you want, and the tone. Beyond that, let the builder decide — over-specifying every colour and pixel rarely helps and the result is one edit away anyway.

Will my form actually save data?

Yes when the project is connected to Supabase. If it is not connected, ask for the saved form anyway: Mythos pauses that build, opens Cloud, and resumes after you connect a project.

Can I ask for a whole multi-page site in one prompt?

You can, but it’s not recommended for a first build. The builder defaults to one landing page; describe that page well, then add routes by chat. One strong page beats a thin version of five.

What if I don't mention colours or fonts?

The builder chooses a palette and type pairing that fit the tone and industry you described. If you have a specific look in mind, name it in the prompt or make it explicit in the editable Plan draft.

Does writing a longer prompt cost more?

No. A build costs 3 credits regardless of prompt length. A clearer prompt is cheaper overall only because it tends to need fewer follow-up edits.

Plan mode — questions and an editable plan draft before the Build runs.
Fixing a build that isn’t right — how to phrase corrections, revert, and when to edit code directly.
Quick start — the full first-build flow.
Credits & pricing — what each build and edit costs.

​Why prompt carefully

​What to put in a prompt

​Example prompts

​If a form must save data

​One page at a time

​How Plan mode helps

​Good to know

​FAQ

​Related

Why prompt carefully

What to put in a prompt

Example prompts

If a form must save data

One page at a time

How Plan mode helps

Good to know

FAQ

Related