Tips & Tricks 7 min read

The Site Brief — shared memory between you and Ullbek

Every Ullbek site has a living HTML file the agent uses to orient itself and remember your brand, structure, and decisions. It is automatic by default — and open to you anytime.

Illustration of a man holding a glowing document panel, with a gold energy stream carrying abstract words toward a radiant open notebook

What is the Site Brief?

The Site Brief is a single HTML file — /_internal/siteinfo.html — that lives inside every Ullbek site. It is the authoritative, living description of what the site is: its purpose, audience, brand colors, fonts, page structure, image style, and the key decisions made along the way.

It is not a settings panel and not a config file. It is a real, styled HTML page — readable in the preview like any other page, with color swatches, font previews, and a site map laid out visually. The only difference from a normal page is that it lives under _internal, so it is never published. Visitors never see it. Only you and Ullbek do.

A shared notebook the agent reads first and writes back to as the site evolves.

Why it exists

Ullbek does not keep a hidden memory of your project between sessions. When you come back tomorrow or start a fresh chat, the agent needs a way to remember what it is building — without you re-explaining everything. The Site Brief is that memory.

At the start of any task, the agent reads the brief to orient itself: what brand this is, what voice to write in, which pages exist, what has already been decided. It is how continuity works without a persistent brain in the background. The brief is the project's context, written down.

What typically lives in the Site Brief
Purpose & audience
Who the site is for, what it sells or explains, and the core promise in one place.
Brand direction
Color tokens, font pairings, voice and tone — often shown as real swatches and type previews, not just descriptions.
Site structure
Which pages exist, what each one is for, and how navigation is organized.
Key decisions
Choices already made — so the agent does not re-ask or quietly reverse them next session.
Imagery style
How photos and generated images should look so every page feels like one brand.

Two readers, one document

The brief is designed to be read by both of the people who work on the site — you and the agent. That is what makes it different from a config file locked away in the back: it is a shared context, written so a human can scan it and a machine can act on it.

Ullbek reads it first

  • Orients on brand, voice, and structure before any change
  • Knows what is already decided — no re-asking
  • Writes back to it as the project evolves
  • Keeps work consistent across sessions

You can read it anytime

  • See exactly what the agent believes about your site
  • Catch drift before it spreads across pages
  • Point at a section and ask for a change
  • Use it to drive the agent deliberately

How to open it

The Site Brief is always one click away — you do not need to remember a path or type a command.

  1. The info icon

    In the preview toolbar, click the info icon (the i). The Site Brief opens in the preview, rendered like any other page.

  2. Or just ask

    Say “open the site brief” or “show me the brief” in chat. Ullbek navigates the preview there for you.

  3. Read it like a page

    Scroll through it. You will see the brand palette as real color blocks, the fonts rendered live, and a map of the site's pages — not a wall of settings.

How it stays current

The brief is a living document. It is not written once and forgotten — it moves with the project. By default, you do nothing. The agent keeps it current as the work progresses.

01 · Bootstrap

Created at the start

When a site is bootstrapped, Ullbek researches the subject and writes the first brief — brand, structure, direction.

02 · Read first

Read before each task

At the start of any request, the agent reads the brief to orient itself and respect what is already decided.

03 · Updated

Written back as things change

When direction shifts — new colors, new pages, a renamed section — the brief is updated so future work follows.

Automatic by default

You do not have to think about the brief. Ullbek creates and maintains it as part of building. Most users never open it — and that is fine. It is there when you need it, invisible when you do not.

When to use it deliberately

For most projects, the automatic maintenance is enough. But the brief becomes genuinely useful as a tool you drive in a few situations — especially as a site grows or goes through a lot of changes.

Lock a direction change

Changing your brand or tone? Update the brief first, then ask for the change. The agent applies it consistently across every page — and remembers it next time.

Large or fast-moving sites

When there are many pages or frequent updates, the brief is what keeps the whole thing coherent. It is the single source of truth the agent checks against.

Make the agent remember something

If there is a rule you want followed forever — “never use stock photos,” “the founder's name is spelled this way” — put it in the brief. It becomes a standing instruction the agent reads each session.

Catch drift before it spreads

Glance at the brief now and then. If the agent's understanding has drifted from what you want, correct it there once — and every following change realigns.

Good hygiene, not homework

Think of the brief like checking a map on a long trip — a quick glance keeps you on course. You do not edit it every session. But when direction matters, pointing the agent at the brief first is the cleanest way to steer.

How to ask for a change

You do not need special syntax. Describe the change in plain language and Ullbek will update the brief — then carry the new direction into the work.

Example prompt
Update the site brief: the brand should feel warmer and more editorial — terracotta and cream, softer voice.
Example prompt
Add a standing rule to the brief: never use stock photography — only my own uploads or generated images.
Example prompt
Open the site brief — I want to review what we decided about the navigation.

What it is not

  • Not a settings panel. There is no form to fill out. It is a readable document the agent reads and writes as HTML.
  • Not a hidden memory. There is no separate, invisible brain. The brief is the memory — and you can look at it whenever you want.
  • Not published. It lives under _internal, so it is never on your public URL, never in the sitemap, and never crawled. See Internal pages for how that privacy works.
  • Not a vault. Unpublished is not encrypted. Do not store passwords, API keys, or secrets in the brief or any site file — keep those out of the project entirely.

Common questions

Do I have to maintain it myself?

No. Ullbek creates and updates the brief as part of building. Most users never open it and everything works. It is there for when you want to steer deliberately or check the agent's understanding.

What if I delete it?

The agent relies on the brief for continuity, so deleting it means the next session starts with less context. If it is gone, ask Ullbek to recreate one from the current state of the site — it will read the pages and write a fresh brief.

Is it the same as the brand kit?

Related, but broader. The brand kit is about identity — colors, fonts, logo, voice. The Site Brief includes the brand direction but also covers purpose, audience, site structure, imagery rules, and key decisions. The brief is the whole project context; the brand kit is one important part of it.

Will visitors ever see it?

No. It lives under _internal and is excluded from every publish. It has no public URL on your free subdomain or custom domain. Only you and the agent can open it in the builder.

See it on your next build

Open the info icon in the preview toolbar to read your Site Brief, or steer the agent by asking it to update the brief first.