Prompts
Round 1: build a plugin. Round 2: check it and fix one thing. Click Copy, paste into your AI tool, and fill in everything in [square brackets].
No idea what to build? See the plugin ideas list for inspiration.
Jump to: Round 1: build · When it doesn't work · Round 2: check and fix
Round 1: build
Reading Time Easy
Shows the estimated reading time above each blog post.
You're done when: a single blog post shows "Estimated reading time" above the text, and your homepage and archive pages don't. Then open a very short post: does it say "1 minute" or "1 minutes"?
External Link Icon Easy
Adds an arrow icon to external links and opens them in a new tab.
You're done when: a link to another website inside a post has an arrow after it and opens in a new tab, and a link to a page on your own site doesn't. Links in your menu and footer probably stay as they are: the prompt only asks for links in posts and pages.
Maintenance Mode Medium
Shows an "under maintenance" page to visitors while admins can still use the site.
You're done when: a private or incognito window (where you're not logged in) shows your maintenance message, and your normal window still shows the site and wp-admin. LocalWP only: this one doesn't work reliably in Playground. Before you switch it on, find the checkbox that switches it off again.
Custom Login Logo Medium
Replace the WordPress logo on the login screen with your own image.
You're done when: the login screen shows your image instead of the WordPress logo, and clicking it takes you to your homepage. To get to the login screen in Playground, log out via your name at the top right of the admin bar; on LocalWP, open /wp-login.php in a private window. Does the "choose image" button do nothing? Tell the AI exactly that and ask it to add the JavaScript for the media uploader. That second round is normal for this one.
Your own idea Freestyle
Have your own idea? Go for it! Use the template from the preparation page and fill in your own details.
Tip: keep it to one feature. "Does one thing well" beats "does everything badly."
When it doesn't work (or it does, and you want more)
The first try often doesn't work. That's not failing, that's the work. Paste what you see back into the AI, and always ask for the complete file back, so you can replace everything instead of hunting for the changed lines.
It breaks
An error message, a white screen, or the plugin won't activate.
Watch for: if two fixes in a row don't help, start a fresh chat with your original prompt plus one sentence about what went wrong. White screen in Playground? Start a fresh Playground and paste the fixed code there. On LocalWP, rename the plugin's folder and WordPress switches it off. "Parse error" when you click Activate? Check that the very first line of the file is <?php. In a test with a small AI model it was missing in four of six first answers, and when we pasted the error back, the AI blamed something else twice in a row.
Change one thing
It works, and you want it to do one thing differently.
You're done when: the one thing changed and everything you checked before still works. Check it again; a "small" change can break something you didn't ask about.
Explain it to me
Before you trust it: what does each part actually do?
Why: one of the questions at the end of the workshop is "can you explain in one sentence what each part does?" This is the honest way to find out. Keep in mind that the explanation comes from the same AI that wrote the code.
Round 2: check and fix
Your plugin works. Now let a tool look at it: Plugin Check, a free plugin from the WordPress project that reads your code and flags known problems. Then use the AI to understand and fix one finding. One finding, not all of them. You have until 12:10. Not running Plugin Check again by 12:05? Stop and write down where you got stuck: that's useful for the discussion afterwards.
- Go to Tools → Plugin Check and choose your plugin. Not under Tools? Plugins → Add Plugin, search for "Plugin Check", install, activate.
- Leave Categories as they are: Plugin Repo ticked (that's the default, and the same as the second run in the demo). It finds everything the Security box finds, plus forms without a nonce and input that isn't cleaned. Unticked it earlier? Tick it again: Plugin Check remembers your last choice. Click Check it!
- Pick one row, Error or Warning, whose Code contains
Security,SettingSanitization,PreparedSQLordirect_file_access. More than one? Take an Error first. Copy that row.
readme, license, uri, PrefixAllGlobals, trademarked or I18n in them are paperwork for the WordPress.org plugin directory. DirectQuery and NoCaching are about database style. None of them tells you whether your site is safe.
Nothing to pick? Normal for plugins without a form or settings page, such as Reading Time and External Link Icon. Use the self-review prompt below. Or, with more than 10 minutes left, use "Change one thing" above to add a settings page (for example: "let me change the reading speed under Settings") and check again. In our two tests with a small AI model, that settings page got a
SettingSanitization row both times.
1. Explain the finding
Understand it before you fix it.
You're done when: you can say in one sentence what could go wrong, and who could make it happen: a visitor, a logged-in user, or only you.
2. Fix that one thing
One finding, the smallest possible change.
You're done when: you've replaced the code, the plugin still does what it did before, you've tried the thing the finding was about yourself (a setting? Save 0, a word, and an empty box), and you've run Plugin Check again with the same categories ticked. Did the number go down? Did a new one appear?
Watch for: a comment containing phpcs:ignore in the new code. It tells Plugin Check to skip that line. In a test with Plugin Check 2.1.0, the finding disappeared from the results while the problem stayed in the code. Look up the function the AI named on developer.wordpress.org/reference: in one of our tests it used sanitize_number_int, which doesn't exist. Also compare what the AI says it changed with what you asked for: in our tests it changed five lines when asked to fix one, and the line numbers in its list were wrong.
Reading Time with a settings page. Plugin Check flagged
SettingSanitization: the reading speed is saved without being checked. We asked for a fix three times. Each time the row disappeared and the errors went from 4 to 3. Each time, saving 0 as the reading speed still broke every blog post with a critical error (division by zero). One of the fixes used a WordPress function that doesn't exist, and WordPress ignored it without a word. Plugin Check checks that there is a cleaning step, not that it's the right one. So after a fix, try the thing the finding is about yourself.
Login Logo, written by the AI. Same
SettingSanitization row. The explanation said visitors could trigger it; only admins can open that settings page. The fix changed a different line, and the row stayed. "Still flagged?" got a wrong reason and a few loose lines instead of the complete file. That's the moment to stop and write it down.
The bad example from the demo, line 34. Five changed lines, errors from 8 to 3. Looks like a win. But the "Remove logo" link could still delete any setting on the site, and all 13 warnings were still there, including
NonceVerification: the link has no nonce, so a crafted link clicked while you're logged in could use it. The errors went down; the warnings didn't. Read the warnings too.
3. Still flagged?
The AI says it fixed it. Plugin Check disagrees.
After two tries, write down what happened and stop. That's useful for the discussion at the end: "Plugin Check still shows errors after two rounds and I can't tell whether they're real" is one of the signs that it's time to ask a developer.
Self-review
For plugins with nothing to pick, or to compare with Plugin Check.
Then compare: does the AI list the same problems as Plugin Check? Did it find something Plugin Check didn't? Does every line it quotes actually appear in your code? Neither of them is the referee, and zero findings from both still doesn't mean safe. In our test on a Reading Time plugin the AI found nothing, which was right, but its line numbers were about ten lines off. Neither of them noticed that 600 words showed "2 minutes" or that it also appeared on pages: that's yours to test.