Create a website with AI: what to describe so it works first time

An AI builds a website from your description: you write in plain words what kind of site you need and what should be on it, and the agent in the Code section on NeuralSpace writes the code, starts the server and hands you a working link. Anything you leave out of the description, the model fills in with defaults — generic sections, generic copy, generic prices. So "it came out wrong" almost always means the brief was short, not that the AI is weak. Below are seven points of a brief, a ready-made example, a list of things to keep out of it, and the exact sequence of clicks on the site.

Why the first result depends on the brief

A single sentence sets off dozens of agent steps: it writes files, starts a server, hits errors, fixes them and restarts. That autonomy is the strength of the section, but it has a price: every gap in your brief is filled with the most typical option. Don't say who the site is for — you get a neutral corporate tone. Don't give prices — you get "from $50" or a placeholder. Don't list the sections — they will be invented for you, and half of them will be useless.

The numbers from the Code section back this up. Across 681 chats between 24 January and 4 November 2026, 61% of first descriptions were shorter than 120 characters, and at least one word about a concrete page section (reviews, prices, form, gallery, contacts) appeared in only 21% of them. In 72% of chats the person writes exactly one message and never refines the project afterwards. In most cases the site is therefore assembled from the model's defaults rather than the author's intent (source: anonymised generation history of the section, aggregates only, no account data).

Seven points of a brief

This is not a ten-page spec: the seven points fit into 700–1200 characters, which is one message.

1. One action. What the visitor should do: send a request, call, book, message you. One goal — everything else serves it.
2. Who it is for. City, age, which device they use, what matters to them. This drives the tone, the font size and the order of sections.
3. Sections in order. The most important point: "hero with a headline and a button → three services with prices → how the work goes in three steps → reviews → address and opening hours → request form → footer with contacts". When the sections are listed top to bottom, the agent has almost nothing to invent.
4. Copy and numbers. The real name, real services, real prices, timelines, names in reviews. Otherwise you will be editing placeholders by hand later — cheaper to type your own text right away.
5. Contacts. Phone, messenger, email, address — and where they should go: in the header, in the footer, as a button after the form.
6. Style in three words. Two or three adjectives, a colour and one reference point: "calm, craft-like, dark green and white, large type". "Beautiful and modern" means nothing — the model will read it its own way.
7. Boundaries. What you definitely don't need: online payments, a user account, an English version, heavy animations. An explicit ban saves an entire round of edits.

A ready-made brief: copy it and swap in your details

This is what a description looks like when a one-page site comes out right on the first run. Replace the niche, prices and contacts with your own.

Build a one-page website for a bicycle repair workshop "[name]" in Manchester. The main action is leaving a repair request. Most visitors come from a phone; the audience is people aged 25–45 who ride in the city and don't want to be without a bike for a week.

Sections top to bottom: hero with the headline "Bike repaired in a day" and a "Book now" button; three services with prices (full service — from £45, inner tube replacement — £12, gear adjustment — £22); how the repair works in three steps; four reviews with names and dates; workshop address and opening hours; request form (name, phone, what happened to the bike); footer with contacts.

Style: calm, craft-like, dark green and white, large type, no stock smiles. Phone and address in the header and in the footer, clickable. Online payment, a user account and an English version are not needed — one page only.

What should stay out of the description

• Half-technical instructions. "Built with React and Redux" won't improve the page: the agent will follow the stack instead of the task. The exception is a real constraint: "one page, no build step".
• Judgements without details. "Make it stylish" and "so it looks expensive" get interpreted however the model likes. Replace them with specifics: colours, font, what must be on the hero.
• Two goals in one brief. "Sell, tell the company story, collect requests and run a blog" is four different websites. Start with one.
• Secrets and other people's data. Passwords, card numbers, passport data, client contacts must not end up in the description or in the project files.
• Twenty pages at once. "A home page and 20 service pages" is a reliable way to get 20 placeholders. Start with one page, or five.

What to enter where on NeuralSpace

1. Open the Code section and sign up. New users get starter tokens credited; after that you pay per token, with no subscription.
2. Click "New project". You will see the "Describe your project" field and one-click templates: Landing page, Portfolio, Storefront, Site for search, Telegram bot, Form / questionnaire, Browser mini-game.
3. If your brief isn't ready, take a template: it inserts a skeleton with square brackets — replace them with your own details. The "Site for search" template is handy because it first asks the model to propose the page structure and only then builds it.
4. Paste the seven-point description. No need to translate: the model answers in the language of your request.
5. Pick a model and run it — the cost of the run is shown before you start.
6. The agent writes the code, starts the server and shows a preview. When you are happy with the result, publish the project and get the site link; a custom domain is bound in the project settings.

You can draft the section copy in advance in the NeuralSpace chat — that is faster than inventing wording inside the project field.

Which model to pick

The Code catalogue includes DeepSeek V4.1 Flash, GLM-5.3 Flash, Kimi K2.6 and Kimi K3, Gemini 3.8 Flash, GPT-6 Luna and GPT-6.1, Claude Sonnet 5.5 and Claude Opus 5.5. For a site built from a ready brief the most powerful model is not required: the main job is to lay out the listed sections neatly, and the affordable models handle it. Start with DeepSeek V4.1 Flash or GLM-5.3 Flash — the first round of edits is cheaper on them. Switch to Kimi K3 or Claude Sonnet 5.5 once the site grows: several pages, forms with logic, a catalogue with filters.

Users' preferences show in the generation history: 60% of chats in the same period ran on Kimi, 9% on Claude Sonnet 4.5, and the median amount of agent work is about 41 thousand tokens per project (p90 — 669 thousand across 572 chats with non-zero spend). In plain terms, most sites are built on an affordable model, and that is enough.

Edits: one change per message

If the result is close to what you wanted, don't rewrite the brief. The formula for an edit: what is wrong + how it should be. A few working examples:

• "Hero: make the headline twice as short, the button bigger and higher, add a line about the guarantee under the button."
• "In the services block add a fourth service: bike assembly after delivery, £30."
• "Keep the form, but add a 'preferred call time' field — a dropdown: morning, afternoon, evening."
• "The page loads slowly: keep one large photo instead of four, make the rest smaller."

If the agent broke something that already worked, don't describe the problem from scratch — ask it to restore that specific block and fix it in a separate message.

Checklist before publishing

• The phone and messenger are clickable from a phone, not just styled as text.
• The form actually submits and the request arrives where you will see it.
• No square brackets, "Lorem ipsum" or placeholder prices are left in the copy.
• The browser tab has a title and a description, not "My project".
• The page opens in a private browser window — which means it really is public.
• On a narrow screen there is no horizontal scrolling and buttons don't overlap.

If the site needs its own address, bind the domain in the project settings and wait for the certificate to be issued — after that you can hand the link to clients and put it into ads.

FAQ

Is one description enough for the AI to build a site?

For a one-pager, a business card site or a portfolio — yes, if the brief lists the sections, the copy and the contacts. A site with a catalogue, forms and several pages usually takes two or three rounds of edits: the first result is a working skeleton, then you refine the details.

Do I need to know how to code?

No. You write the description in plain language and the agent writes the code. Understanding what a page is made of helps you phrase things more precisely, but it doesn't replace the brief: half of all edits come from missing sections, not from not knowing syntax.

How much does it cost to build a site with AI on NeuralSpace?

New users get starter tokens credited, which is enough for a first project. After that you pay per token with no subscription; the cost of a run is shown before you start and depends on the model you pick. The tighter the brief, the fewer rounds of edits and the lower the spend.

What if the result is completely wrong?

Don't rewrite the whole brief. Point at the single most obvious problem and ask for a fix — one item per message. If there are many problems in different sections, creating a new project with a more detailed description is faster than fixing ten little things one by one.

Where can I try it right now?

In the Code section on NeuralSpace: sign up, click "New project", paste the seven-point brief — and in a few minutes you have a link to the first version of your site.