Members, courses and events, the site around them, built.
Membership, LMS and event plugins own their own data. WPPilot builds everything around them: the pricing page, the gated templates, the comparison table, the event entries, the enrolment and level operations, so the plugin keeps being the source of truth while the site around it gets built in an afternoon.
Membership site brief
This is the whole input.
Be explicit about which system owns what. The agent operates the plugin's data through typed abilities; it does not reimplement access control in a page builder.
Paste into your AI client
PROJECT TYPE: MEMBERSHIP / COURSE / EVENTS SITE
MEMBERSHIP OR LMS: [PAID MEMBERSHIPS PRO / TUTOR LMS / THE EVENTS CALENDAR / BUDDYPRESS]
BUILDER: [BRICKS / DIVI 5 / OXYGEN 6 / BREAKDANCE / ETCH]
ORGANISATION: [NAME] offering [MEMBERSHIP / COURSES / EVENTS] to [AUDIENCE].
PAGES: Home; what membership includes; level or course comparison; individual level or course pages; events listing; member resources; FAQ; join; account handoff; Contact; Privacy.
LEVELS OR COURSES: Read the existing levels, courses and event data first and build pages from what is actually configured. Do not invent a tier that does not exist in the plugin.
GATING: Build member-only templates with display conditions. Access control stays with [PLUGIN], do not simulate it with hidden elements.
EVENTS: Create events for [LIST] with date, time, venue, description and ticket link. Anything I have not supplied is [CONFIRM].
COMPARISON TABLE: Build it from the real level or course data, not from marketing copy.
OPERATIONS: For enrolments and level assignments, show me the list of users you plan to act on and wait for approval.
CLAIMS: Prices, renewal terms, refund policy, seat counts, accreditation and outcomes are [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
Reads what the plugin already has
Membership levels, courses and their content, existing events. Pages get built from configured reality rather than from a brief that guessed at the tier names.
- 2
Builds the public site around it
Pricing page, level or course comparison, individual pages, FAQ and join path, composed as full document trees in your builder, using your design tokens.
- 3
Creates gated templates with real conditions
Member-only templates use the builder's display-condition system. Access control stays with the membership plugin; the agent does not fake it by hiding elements client-side.
- 4
Creates the events
The Events Calendar entries with date, time, venue, description and ticket references, created through typed abilities and reported back as a list.
- 5
Runs enrolment and level operations under review
Enrolling users in Tutor LMS or assigning a Paid Memberships Pro level are real operations on real people. The agent shows the target list first and waits.
- 6
Leaves the money claims alone
Prices, renewal terms, refund policy and accreditation come back marked [CONFIRM]. These are the claims that turn into disputes when they are wrong.
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.
Events
Builders
Forms and payments context
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- Membership levels are created in Paid Memberships Pro, not by the agent. It lists levels, assigns and cancels them for users, and reads memberships, level configuration stays in the plugin.
- Courses are created in Tutor LMS. The agent lists courses and content, enrols and unenrols users, and builds the site around them.
- Enrolment and level changes affect real people's access. Treat them as reviewed operations, and use Pro's approval queue if more than one person can drive the agent.
- Payment and renewal configuration is out of scope entirely. That lives in the membership plugin and its gateway.
- The agent cannot create WordPress users. User creation is classed critical and is blocked under the default safety profile.
Questions
Build a membership or events site, answered
Can it create my membership levels or courses?
No, those are configured in Paid Memberships Pro and Tutor LMS themselves. What it does is read them and build the entire public site around them, plus run enrolment and level-assignment operations for existing users.
How is content gated?
Through the builder's display conditions plus the membership plugin's own access control. The agent will not simulate gating by hiding elements, content that is merely hidden is still served.
Can it add all my events at once?
Yes, from a supplied list: date, time, venue, description and ticket link per event. Anything missing from the list comes back as [CONFIRM] rather than being filled in.
Will it sign people up automatically?
Only when you ask, and it shows you the list of users first. Enrolment changes someone's real access, so it is a reviewed operation rather than a side effect.
Your site · your policy · your AI client
Send the brief. Get the membership and events site.
Install WPPilot Free to connect your AI client, then add Pro for the builder, commerce and plugin modules this run depends on.