One brief. Every page.
A project brief describes the business, the pages, the art direction and the proof you actually have. The agent turns it into real builder documents: header and footer templates, page layouts built from your global classes, a menu, a front page setting and a contact form, inside the builder you already own.
Project brief
This is the whole input.
This is the shape Pro's bundled build-page skills are tuned for. Vague briefs get vague sites; this format names the pages, the design language and the facts the agent is not allowed to invent.
Paste into your AI client
PROJECT TYPE: COMPLETE WEBSITE
BUILDER: [BRICKS / DIVI 5 / OXYGEN 6 / BREAKDANCE / ETCH / BEAVER BUILDER / WPBAKERY / MOSAIC]
INDUSTRY: [INDUSTRY]
BUSINESS: [BUSINESS NAME] in [CITY/REGION], serving [CUSTOMER TYPE].
GOAL: [THE ONE ACTION A VISITOR SHOULD TAKE].
PAGES: Home; [SERVICE PAGES]; About and team; [PROOF PAGE]; Pricing approach; Contact; Privacy.
ART DIRECTION: [PALETTE], [TYPE PAIRING], [GRID], [PHOTOGRAPHY STYLE]. Name what to avoid as well: stock handshakes, glassy gradients, fake dashboards.
DESIGN SYSTEM: Read the existing global classes, variables and theme styles first. Reuse them. Create new tokens only where nothing suitable exists, and tell me what you added.
TEMPLATES: Build header and footer templates with their display conditions, and an archive template if the brief has a content archive.
NAVIGATION: Create the primary menu, assign it to the theme location, and set the front page and posts page.
FORMS: Contact form on [FORM PLUGIN] with fields [FIELDS]. Inspect the schema before building. Do not connect notifications until I approve recipients.
PROOF: Testimonials, client names, credentials, statistics, awards and prices are [CONFIRM] unless I supplied them.
STATUS: Everything stays draft or unpublished. Report what you built, what you reused and what needs a decision.One prompt from you becomes hundreds of typed ability calls from the agent, each one checked against your WordPress capabilities, the active safety profile and the confirmation rules before it runs.
What happens next
The run, step by step
Nothing here is a black box. Every step is a typed call you can see in the change log afterwards.
- 1
Inventories the site it is about to change
Active builder, existing templates and their display conditions, global classes, variables, theme styles, menus, registered post types and installed form plugin. A header template change can hit every route on the site, so it is read before it is touched.
- 2
Establishes the design system first
Colours, typography and spacing become variables and global classes before any page exists. Every page built afterwards references them, which is why the tenth page still matches the first.
- 3
Builds the templates that frame everything
Header, footer and any archive template, with explicit display conditions. In Divi 5 that is a Theme Builder template; in Bricks, Oxygen, Breakdance, Beaver Builder, WPBakery, Etch and Mosaic it is that builder's own template type.
- 4
Writes each page as a complete document tree
One call per page writes the whole element tree, sections, columns, elements, bindings, rather than nudging one widget at a time. Structure is composed from the builder's real element schemas, so it opens in the native editor afterwards.
- 5
Wires navigation and the front page
Menu created, items ordered, assigned to a theme location, front page and posts page set through update-site-settings. The site stops being a pile of drafts and becomes something you can click through.
- 6
Adds the form, then stops before the risky part
Fields are built against the form plugin's schema. Notification recipients, CRM routing and success behaviour are left for you to approve. The agent does not send a live test lead on its own.
Plugins it can drive
It works with what you already run.
WPPilot Pro ships 53 integration families. A module only registers once its plugin is detected on the site and a Pro licence is active.
Themes
Forms
Content and SEO
Multilingual
Under the prompt
The abilities this run actually calls
Real registered ability names from the shipped plugin source. Each one has a schema, a permission check and a risk classification.
Where it stops
What stays yours.
Speed is only useful if you can trust the result. These are real constraints in the plugin source, not a disclaimer paragraph.
Read the security model- The agent builds in the builder you already have. It cannot install or activate a plugin or theme, no install ability exists anywhere in WPPilot, in any safety profile.
- Core-block and block-theme layouts are the exception to headless building: they queue changes for the Block Editor Queue screen, where a browser tab finalises them. Builder-based sites do not need that step.
- Pages are created as drafts by default. Publishing is a separate, explicit instruction with its own capability check.
- Header, footer and archive templates apply site-wide. Their display conditions are read before the write and reported after it, and Pro can hold them in an approval queue.
- Facts stay yours. Prices, credentials, client names, statistics and legal text come back marked [CONFIRM] rather than filled in with something plausible.
Questions
Build a business website, answered
How many pages can it build in one run?
As many as the brief lists. The practical limit is the write rate, 120 writes per minute per credential, so a ten-page site with templates and a menu is a paced run you can watch in the change log, not an instant flash.
Which builder should I pick for this?
Bricks, Divi 5, Oxygen 6, Breakdance, Etch and Mosaic have the deepest coverage: whole-tree writes plus their own template systems for headers and footers. Elementor writes full document trees too, but has no template or theme-builder ability, so its headers and footers stay a manual step.
Will it match our brand, or will it look like a template?
It reads your existing global classes, variables and theme styles before it builds and reuses them. The art direction section of the brief is where you set palette, type pairing, grid and what to avoid. That section is doing most of the work in how the result looks.
Can I use this on a client's live site?
Build on staging, review in the native editor, then repeat the run against production with the same brief. Pro's approval queue parks every write for human sign-off if you want a second gate on client work.
Do I need to know what MCP is?
No. You install the plugin, connect your AI client once with the generated configuration, and write briefs in plain language after that. The protocol is plumbing.
Your site · your policy · your AI client
Send the brief. Get the business website.
Install WPPilot Free to connect your AI client, then add Pro for the builder, commerce and plugin modules this run depends on.