Builders with template systems
BricksDivi 5Oxygen 6BreakdanceEtchMosaicBeaver BuilderWPBakery
Build a portfolio site
Show the work. Let the agent build the shell.
A portfolio is a content model wearing a nice layout. The agent builds the project post type with fields for client, year, sector, credits and rights, a filterable archive, a single-project template, and galleries where the photography credit is a field rather than an afterthought.
Portfolio brief
This is the whole input.
The credit and rights fields matter more than they look. Photography permissions are the thing portfolios get sued over, so they belong in the model from day one.
Paste into your AI client
PROJECT TYPE: PORTFOLIO SITE
BUILDER: [BRICKS / DIVI 5 / OXYGEN 6 / BREAKDANCE / ETCH / MOSAIC]
FIELDS PLUGIN: [ACF / ACPT / META BOX / PODS / JETENGINE]
DISCIPLINE: [ARCHITECTURE / PHOTOGRAPHY / DESIGN / DEVELOPMENT / FILM].
STUDIO: [NAME], working in [SECTORS] across [REGIONS].
MODEL: Project post type with fields for client, year, status, sector, location, services, collaborators, photography credit, usage rights, summary, challenge, response, outcome and gallery.
TAXONOMY: [SECTOR / SERVICE / LOCATION] as filters on the archive.
ARCHIVE: Filterable grid, [N] per page, ordered by [YEAR / FEATURED]. Show client, year and sector on the card.
SINGLE TEMPLATE: One continuous editorial scroll: identity strip, hero image with credit, brief, constraints, response, image sequence, credits, related projects, enquiry CTA.
ART DIRECTION: [PALETTE], [TYPE], crop discipline. Every image crop is intentional; no masonry chaos.
RIGHTS: Never publish an image without a credit field value. Missing rights are [CONFIRM] and the project stays a draft.
ENQUIRY: [FORM PLUGIN] with project type, stage, timeline and budget range. Routing is [CONFIRM].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
Models the project properly
Client, year, status, sector, collaborators, credit, rights. A portfolio built on plain posts hits a wall the first time someone asks to filter by sector; this does not.
- 2
Creates the taxonomy that drives filtering
Sector, service and location as real taxonomies with their terms, so the archive filters are query-driven rather than hand-maintained lists.
- 3
Builds the archive template
A loop bound to the project fields, with the card showing what a visitor actually scans for, client, year, sector, instead of a truncated paragraph.
- 4
Builds the single-project template
One template that every project uses. Written once against the builder's element schemas, bound to fields, so adding project forty needs no design work.
- 5
Imports and credits the media
Images imported, attached, alt text written, credits mapped into the credit field. Anything without rights information stops rather than publishing.
- 6
Adds the enquiry path
A form with the fields that actually qualify a project, type, stage, timeline, budget range, built against the form plugin's schema and left disconnected until you approve routing.
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.
Content modelling
ACFACPTMeta BoxPodsJetEngineEtch
Enquiry forms
WPFormsGravity FormsFluent FormsFormidableContact Form 7Ninja Forms
Themes
AstraGeneratePressOceanWPBlocksyNeveKadence
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.
acf-create-post-typeacf-create-taxonomyacf-create-fieldgroupacpt-create-post-typepods-create-cptbricks-create-templatebricks-set-template-conditionsdivi-create-theme-builder-templatemosaic-create-templateimport-media-urlattach-mediaset-featured-imagecreate-termassign-termscf7-create-form
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- Image rights are not something an agent can verify. Missing credit or licence information stops the project at draft.
- Archive and single templates apply to every project. Their conditions are read before the write and reported after it.
- Deleting a post type or taxonomy is destructive and requires explicit confirmation. The content inside it does not come back.
- Awards, client names, project values and completion dates come back marked [CONFIRM] unless you supplied them.
Questions
Build a portfolio site, answered
Can it migrate my existing projects into the new model?
It can read existing posts and create new project entries from them, field by field. Treat it as a supervised migration on staging, with a diff at the end, rather than an unattended import.
What if I already have a portfolio post type?
The agent inspects registered post types and field groups first and works with what exists. Creating a second, competing project type is the kind of thing it reports back rather than doing quietly.
Does it handle galleries and image credits?
Images are imported, attached, given alt text and mapped to a credit field. That field is part of the model precisely so an uncredited image is visible as missing data rather than invisible risk.
Your site · your policy · your AI client
Send the brief. Get the portfolio site.
Install WPPilot Free to connect your AI client, then add Pro for the builder, commerce and plugin modules this run depends on.