If you are a non-technical but want to build stuff in WordPress with AI, bookmark this.
This is the cheat sheet I wish I had when I started vibe coding.
The trick is simple:
Know what to ask AI to use.
After reading this, you’ll know when to ask for blocks, plugins, the REST API, the Interactivity API, and local storage.
And you’ll get much better results.
If you want things to update instantly on the page…
Things like:
- live search
- instant filters
- calculators
- pricing tools
- expanding sections
- menus that update without refreshing
Tell AI:
Use the WordPress Interactivity API.
You do not need to understand how it works.
Just know this:
It makes WordPress behave more like an app.
Instead of:
click → page reload → wait
You get:
click → update instantly
Good prompt:
Build this using the WordPress Interactivity API. Keep it simple, fast, and easy to maintain.
If you want a better editing experience…
Things like:
- easier client editing
- reusable layouts
- editable content sections
- simpler content updates
- custom writing experiences
Tell AI:
Build this as a WordPress block.
Blocks are simply editable pieces of content.
Think:
- FAQs
- testimonials
- pricing tables
- hero sections
- reusable layouts
Good prompt:
Create this as an editable WordPress block and make it easy for non-technical users to update.
If you want another app to publish into WordPress…
Things like:
- writing apps
- automation
- dashboards
- syncing content
- AI workflows
Tell AI:
Use the WordPress REST API.
Ignore the scary name.
Simple explanation:
It lets software talk to WordPress.
For example:
You write something in an app.
You press publish.
It appears in WordPress.
Good prompt:
Build this using the WordPress REST API and keep setup as simple as possible.
If you want to build simple tools quickly…
Things like:
- writing apps
- planners
- saved drafts
- lightweight dashboards
- quick experiments
Tell AI:
Use browser local storage.
This one changed how I think about building software.
Sometimes you do not need databases, servers, or accounts.
The browser can store information locally.
Benefits:
- faster to build
- cheaper to run
- more private
- easier to prototype
Good prompt:
Store content in browser local storage and publish to WordPress via the REST API.
If you want to change how WordPress behaves…
Things like:
- admin tweaks
- WooCommerce rules
- workflows
- permissions
- automation
Tell AI:
Build this as a lightweight WordPress plugin.
Simple rule:
Plugins change behaviour.
One important tip:
Always run Plugin Check https://wordpress.org/plugins/plugin-check/ afterwards.
AI is very good at building things quickly.
It is also very good at quietly creating chaos.
Good prompt:
Run Plugin Check and fix any issues while keeping the plugin simple.
One final tip
Most people say:
Build me a plugin.
That is usually too vague.
Sometimes you need a block.
Sometimes you need the REST API.
Sometimes you need the Interactivity API.
Sometimes you just need local storage.
The more specific you are about what AI should use, the better the result.
That one change alone will dramatically improve your vibe coding.
Leave a Reply