How a build goes
An assistant builds in the same order every time, and Bevel MCP keeps it on track:- Read the site and its current design.
- Write a direction. A few lines before touching anything: mood, a palette with one accent, a type pairing, one signature detail, and how the home page opens.
- Design system. Colours, typography, the button style and its hover animation.
- Logo. From Brand assets, from the business’s website, or a generated wordmark.
- Header, with its menu.
- Pages. Each one added to the menu, and the home page set as the front page.
- Footer, built to match. A build is not finished while the starter header or footer is still live, and the assistant is reminded until it is.
Briefing the assistant
A short brief works. What helps most:- Who it is for and what they do. The industry picks the logo mark, the section shapes and the photography.
- A reference, if you have one: a site you like, a screenshot, a Framer template. The assistant builds to its style.
- The words. Real copy beats “lorem” every time; the assistant writes well from bullet points.
- The files. Drop them into Brand assets first.
Build a site for Northline Roofing, a family roofing contractor in Leeds. Repairs, re-roofs, gutters, inspections. Warm and plain-spoken, no stock-photo gloss. Five pages: Home, Services, About, Reviews, Contact. Logo and photos are in Brand assets.