WPPilot Design

Your AI finally has taste. On WordPress.

AI-built pages tend to look the same because nothing tells the model what your site is. WPPilot Design gives it one direction of its own, saved in WordPress, so every page an agent builds looks deliberate rather than generic.

Why AI pages look alike

The model is not guessing at your brand. It has nothing to guess from.

Every session starts empty, so it reaches for the same safe defaults it reached for last time, on every site it has ever touched.

An agent asked to build a landing page with no direction will produce something competent and anonymous: a centred hero, a three-column feature row, a gradient somebody at a model lab liked, and body copy that fills space without saying anything. It is not a failure of the model. It is the correct answer to a question that never specified anything, and it is why the second page rarely matches the first.

The usual fix is to describe the brand in the prompt. That works exactly once. The next session has no memory of it, a different client has a different context window, and the person who joins the team next month describes it slightly differently. Within a month the site has three blues, two heading fonts, and a section rhythm that changes depending on which day the page was built.

WPPilot Design moves that decision out of the prompt and into the site. The direction is a document stored in WordPress, read before any visual work begins, and checked against before anything is finalised. It is the difference between telling an agent what you want and giving it something it can be held to.

One prompt, every page

It sets the direction. Your builder still builds the page.

The design document is builder-agnostic on purpose: it describes the site, not the tool, so the same direction applies wherever the page is actually made.

ElementorBricksBreakdanceDiviOxygenBeaver BuilderWPBakeryFlatsomeEtchMosaicGutenbergGenerateBlocksKadence BlocksSpectraSpectra OneAstraAvadaGeneratePressKadenceOceanWPWordPress Block ThemesBlocksyNeveWoodMart

Depth varies by surface, and the integration pages say where. A builder with a Pro module gets the direction expressed in its own primitives, global classes and templates rather than approximated with inline styles, which is the difference between a page a designer can keep editing and one they have to rebuild.

How it goes

Set it once, then stop deciding.

Three steps, and only the first one needs your judgement.

  1. 01

    Tell your AI to use WPPilot Design

    In plain words, in whichever client you already use. The agent reads the active design before it writes anything, so the direction is set before the first element exists rather than corrected afterwards.

  2. 02

    Judge it on a real page

    Not a mockup and not a description of a mockup. Build one page, open it in the builder that owns it, and decide whether the direction is right while changing it is still cheap.

  3. 03

    Build the rest to match

    Every page from that point reads the same document. The twentieth page is not a fresh interpretation of your brand, it is the same contract applied again.

What a direction contains

A direction is a design system.

Not a vibe in a prompt that vanishes next session. Fonts, colours, spacing, voice and rules, saved in your WordPress and applied to every page your AI builds.

The document is plain Markdown, which matters more than it sounds: you can read it, a person who is not a designer can argue with it, and it diffs like anything else you version. The structured contract the abilities return is generated from it, so there is one source and no second copy to drift.

Read the design abilities
TY

Type

The display and text families, their weights, and the scale between heading levels.

CO

Colour

The palette as named tokens, with which one is the accent and how much of it is too much.

SP

Spacing

The rhythm sections sit on, so vertical space is a decision rather than whatever the builder defaulted to.

VO

Voice

How copy reads. Plain and direct, or warm, or technical, stated once instead of re-negotiated per prompt.

RU

Rules

The Don'ts. One accent colour. Real numbers, never placeholder statistics. No stock photography.

The pre-flight check

AI-built pages that skip the AI slop.

Before an agent finalises a page it can run the candidate output, the HTML and CSS or just the visible text, against the active design. The check returns a result per rule: your own tokens and Don’ts, plus a set of universal checks for the tells that give an AI-built page away. Failures come back as failures, not as advice, and the instruction is to fix every one before shipping.

This is the part that makes the direction enforceable rather than aspirational. A rule in a system prompt is a request the model may drop three thousand tokens later. A rule the site checks is a rule.

Caught by default

  • Em-dashes sprayed through body copy
  • The default AI purple gradient nobody chose
  • Inter, on a site whose brand font is not Inter
  • Filler copy that says nothing at length
  • Fonts and colours that are not in the palette

Plus every Don’t you wrote into your own design document, and every font and colour that is not in your palette.

What ships

7 abilities, in the free plugin.

No licence, no external service. The design library lives on your site, and so does the check.

Write

Activate Design

Make a ready design system (by slug) active for this site. Incomplete saved drafts are rejected until their required colors and typography are repaired.

Read

Check Design (Pre-flight)

Pre-flight a candidate page (its HTML/CSS or visible text) against the active design's tokens and Don't rules plus universal anti-slop checks (em-dash, AI-purple, Inter, filler copy, off-palette fonts/colors). Call before finalizing any visual output and fix every "fail" before shipping.

Destructive

Delete Design

Delete a saved design system by slug. If the deleted design was active, the site is left with no active design.

Read

Get Active Design

Return the active site design system as raw DESIGN.md plus structured tokens, dials, guidance, provenance, and readiness. Read this before visual work and build within the returned contract.

Read

Get Design

Return a specific design system by slug as raw DESIGN.md plus its structured contract and readiness. Use to read, repair, or evolve a saved direction.

Read

List Design Library

List saved design systems, readiness, sync readiness, and which is active.

Write

Save Design

Create or update a design system from raw DESIGN.md and return its structured contract. Incomplete new documents are saved as drafts but not activated; an incomplete write never overwrites the active design.

Design abilities obey the same rules as everything else in WPPilot. The active safety profile decides which of them an agent can reach, deleting a design is marked destructive and needs an explicit confirmation, and every write is recorded in the change ledger. A design system is not a special case that skips the controls.

Questions

Before you give it a direction.

WPPilot Design is included in the free plugin and intended for development and staging sites first, like everything else that writes.

Is this a page builder or a theme?

Neither. WPPilot Design is a document stored in your WordPress that describes how the site should look and read, plus the abilities an AI client uses to read and check against it. The pages themselves are still built in whichever builder or theme you already run, which is why the direction survives a builder change and a theme change.

How is this different from putting the brand in a prompt?

A prompt lasts one session. Ask for a page a week later, in a different client, and the model reconstructs your brand from whatever it can infer, which is how a site ends up with three slightly different blues. The design document is saved on the site, so every agent that connects reads the same contract, and there is one place to change it when the brand changes.

Do I have to write the design document myself?

No. The usual route is to describe what you want in conversation and let the agent write the document, then read it back and edit the parts it got wrong. What matters is that the result is saved and reviewable rather than implicit: a document you can open and argue with is worth more than a prompt you have to remember.

What stops the agent from ignoring it?

The pre-flight check. Before finalising a page, the agent can run the candidate output against the active design's tokens and Don't rules, plus a set of universal anti-slop checks, and gets back a pass or fail per rule. It is not a suggestion in a system prompt; it is a call that returns failures the agent has to fix.

Can I keep more than one design?

Yes. Designs are saved in a library by slug, one is active at a time, and you can switch between them. Incomplete drafts are kept as drafts rather than activated, and an incomplete write never overwrites the design currently in use, because a half-finished direction is worse than the old one.

Is it in the free plugin?

Yes. The design module ships in WPPilot Free with 7 abilities and needs no licence. WPPilot Pro does not add design abilities; it adds depth in specific builders and plugins, which is what turns a good direction into a page that uses your builder's real primitives rather than approximating them.

Will the result be as good as a designer?

No, and anyone claiming otherwise is selling something. What it reliably prevents is the other failure: twenty pages that each look like a different site, built by an agent with no memory of the last one. The final page also depends on the model and client you connect, and a more capable model produces a noticeably better result from the same document.

Your site · your policy · your AI client

Give it a direction.

Download WPPilot Free, describe the site you actually want once, and let every page after that be built to the same contract.