Brand kit
These abilities register when Brand kit is detected on the site and a Pro licence is active. If either is missing the module stays absent rather than failing at call time.
At a glance
Brand kit registers 8 abilities: 7 that only read, 0 that write, and 1 marked destructive. That split is the practical answer to how much of this module can run unattended. Reads cost nothing and are safe to repeat, so discovery is the part to be generous with; the writes are where review belongs, and the destructive calls stop for an explicit confirmation every single time regardless of which profile is active.
Availability on your site
The Brand kit module needs three things at once: WPPilot Free as the MCP foundation, an active Pro licence, and the companion plugin detected on the site. Miss any one and the module does not register, which is deliberate: an ability that appears in the tool list but fails at call time is worse than an ability that was never offered. What the connected agent can actually call is then narrowed twice more: by the safety profile active on the site, and by the WordPress capabilities of the user behind the credential. A read that succeeds for an administrator can be absent entirely for an editor.
Every write these abilities perform is recorded in the change ledger, and destructive calls can be routed through the approval queue so a person signs off before anything is applied. A successful tool result means the operation returned, not that the front end, the cache, and every dependent template are correct: that still needs a look.
Reads
Available in every safety profile, including Read Only. Inspection costs nothing and is not rate limited.
| Ability | What it does |
|---|---|
wppilot/brand-kit-export-tokensExport Design Tokens (DTCG) | Exports the active design as a Design Tokens Community Group document — the W3C-backed format Figma, Tokens Studio, Style Dictionary and Penpot all read. Colours, font families and weights, spacing and radii become typed DTCG tokens; the parts DTCG has no vocabulary for (the design's Do and Don't rules, and the variance/density/motion dials) ride in $extensions under this plugin's namespace, so a round trip through another tool keeps them. Pass slug to export a design other than the active one. |
wppilot/brand-kit-from-paletteDesign From a Palette | Turns a flat list of hex colours - the four swatches copied from a palette site, a client's brand colours, anything - into a DESIGN.md draft with the roles assigned and the contrast checked. This is the part that makes a pasted palette usable: a swatch list says nothing about which colour is the page, the text or the button, and pasted straight into a builder it produces a site that uses all four equally or a button nobody can read. Lightness decides the ground and the ink, chroma decides the accent, leftovers are kept as support colours, and any colour that cannot carry text is moved along its own hue until it can, with the move reported so the original stays available for print. Nothing is saved and nothing is applied. |
wppilot/brand-kit-generate-from-briefGenerate Design From Brief | Builds a DESIGN.md scaffold from a description of the business, with the arithmetic done properly: given a seed brand colour it derives a background, ink, accent and muted that are guaranteed to clear WCAG contrast by construction, and reports every ratio. The typeface pairing is chosen from a small curated set by the brief's own words, and names the shipped example direction that demonstrates it. Everything that cannot be derived from a brief — what the site must never look like, what the accent is spent on, the component treatments — is deliberately left blank in a "Still to decide" section, because a plausible guess there gets followed. Nothing is saved; review it, fill in the blanks, then save with wppilot/save-design. On a site that is not brand new, run wppilot/adopt-design-from-site first: the existing brand beats a generated one. |
wppilot/brand-kit-import-tokensImport Design Tokens (DTCG) | Reads a Design Tokens Community Group document — a Figma variables export, a Tokens Studio file, anything speaking the W3C format — and turns it into a WPPilot design. Group-level $type is inherited as the spec requires, and {group.token} aliases are resolved to the value they point at, so a semantic palette built on primitives arrives as real colours rather than unresolved references. Composite typography tokens are unpacked into family, weight and size. Types this mapper does not claim to understand, such as shadow and gradient, are reported in skipped rather than flattened into something plausible. Returns the design markdown; nothing is saved until you pass it to wppilot/save-design. |
wppilot/brand-kit-list-targetsList Brand Kit Targets | Lists the places on this site a design direction can be written to: the block theme's global styles, and the global colour and typography stores of whichever builders are installed. A target is listed only when the ability that writes it is registered, which means its plugin is active and past its version floor. Call this before wppilot/brand-kit-apply to see what applying will touch. |
wppilot/brand-kit-previewPreview Brand Kit | Reports exactly what wppilot/brand-kit-apply would write into this site's design systems, without writing anything. Read-only, so it needs no confirmation, which is the point: a preview that required the same approval as the write would teach people to approve without reading. Same arguments as apply. |
wppilot/brand-kit-verify-appliedVerify Design Is Applied | Fetches a rendered page and checks it against the active design: which of the design's colours and faces actually appear in what the server sent, which are absent, and which colours in use are neither in the design nor a neutral. The finding worth running it for is the negative one — a design that is saved, activated, and shown as active everywhere, but whose accent appears nowhere in the served page. Reads served HTML and inline CSS only: it does not run JavaScript, fetch external stylesheets, or compute the cascade, and the result says so. Run it after applying a brand kit, and after any theme or builder change. |
Destructive
Marked destructive in the source, so each call needs an explicit confirmation flag, every time.
| Ability | What it does |
|---|---|
wppilot/brand-kit-applyApply Brand Kit | Writes the active design's palette and type stack into the site's own design systems, so pages can be built by reference to a global rather than by pasting a hex. This is what makes a later change of direction re-skin the site instead of stranding hundreds of literals, and it upgrades the design gate's advice from "use #B4532A" to "use the global". Pass targets to choose which systems to write, or omit it for every available one. Call wppilot/brand-kit-preview first to see exactly what this would do; that one is read-only and needs no confirmation. Destructive: it changes site-wide design settings that affect every page, and existing globals with the same names are overwritten. |