Teaching the builder your world

Out of the box, the builder knows how products work in general and nothing about yours in particular — your brand, your menu, your house style, the twelve facts every page must get right. You could paste all that into every prompt, and people do, for about two builds. Then they find the four features built for exactly this.

Knowledge files: the facts

Upload documents — price lists, bios, product specs, brand guidelines, that PDF marketing wrote — and attach them to a chat or to your whole account. The builder reads them at build time and treats them as ground truth. The difference shows immediately in the details: real opening hours instead of plausible ones, your actual product names, prices that match reality. Agents are excellent at inventing plausible content, which is precisely the problem when you have true content.

References: the taste

Attach reference sites or images — competitors you admire, a layout that works, screenshots of a vibe — and the builder designs toward them. This pairs with the design director: instead of the director inventing an art direction from scratch, your references constrain it. "Like this, but ours" is a brief the system understands.

Your images: the real thing

The image library holds your actual photos and assets, available to every build. AI-generated illustration is genuinely good now, but a restaurant's site should show the restaurant's food, and a founder's face should be the founder's face. Uploaded images get used where they belong; generation fills the gaps around them.

Templates: the head start

Any build you like can be saved as a template — yours, reusable, with its structure and style intact. The next project starts from it instead of from zero. Agencies and repeat builders end up with a private library: the portfolio starter, the booking-site starter, the one with the client's design system already baked in.