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].

How this works: click "Copy" on a prompt, paste it into your AI tool, and follow the instructions you get back. Every prompt has a "You're done when" line: if you can't see that on your own site, it isn't done yet. Tell the AI what went wrong and try again; that's the iterating part.

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.

Create a WordPress plugin with the following specifications: Name: Reading Time Function: Shows the estimated reading time above each blog post. Where visible: On the frontend, above the content of each individual post. Behavior: Count the number of words in a post, divide by 250 (average reading speed), and show the result as "Estimated reading time: X minutes" above the post content. Round up to the nearest minute. Show a minimum of 1 minute. Only show this on individual blog posts, not on overview or archive pages. Technical requirements: - Follow WordPress best practices (hooks, filters, sanitization) - Include a plugin header with name, description and version - Prevent direct file access - Put all code in a single PHP file, and give me the complete file in one code block that starts with <?php - Add short comments explaining what each part does

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.

Create a WordPress plugin with the following specifications: Name: External Link Icon Function: Automatically adds an arrow icon to all external links in posts and pages, and opens them in a new tab. Where visible: On the frontend, on all links in the content that point to a different website. Behavior: Check every link in the content. If the link points to a different website than my own site, add a small arrow symbol after the link text, make the link open in a new tab, and add a security attribute so the new tab can't access my site. Leave links to my own site and links that point to sections on the same page unchanged. Technical requirements: - Follow WordPress best practices (hooks, filters, sanitization) - Include a plugin header with name, description and version - Prevent direct file access - Put all code in a single PHP file, and give me the complete file in one code block that starts with <?php - Add short comments explaining what each part does

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.

Create a WordPress plugin with the following specifications: Name: Simple Maintenance Mode Function: Shows an "under maintenance" page to visitors when I turn it on. I can still see and use my site normally when I'm logged in as an admin. Where visible: A settings page in the WordPress admin under Settings, and a maintenance message for visitors. Behavior: Add a settings page with a checkbox to turn maintenance mode on or off, and a text field where I can write the message visitors will see. When turned on, visitors see my message and nothing else. The login page should always remain accessible so I don't lock myself out. Show a notice in the admin toolbar so I remember maintenance mode is active. Technical requirements: - Follow WordPress best practices (hooks, filters, sanitization) - Include a plugin header with name, description and version - Prevent direct file access - Put all code in a single PHP file, and give me the complete file in one code block that starts with <?php - Add short comments explaining what each part does

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.

Create a WordPress plugin with the following specifications: Name: Custom Login Logo Function: Lets me replace the WordPress logo on the login screen with my own image. Where visible: A settings page in the WordPress admin under Settings, and my custom logo on the login screen. Behavior: Add a settings page where I can choose an image from my media library to use as the login logo. Show a preview of the current logo on the settings page. On the login screen, replace the default WordPress logo with my chosen image. Also make the logo link go to my homepage instead of wordpress.org. Technical requirements: - Follow WordPress best practices (hooks, filters, sanitization) - Include a plugin header with name, description and version - Prevent direct file access - Put all code in a single PHP file, and give me the complete file in one code block that starts with <?php - Add short comments explaining what each part does

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.

My WordPress plugin doesn't work. This is what I did and what happened: [for example: "I clicked Activate and got this message", or "nothing shows up on my posts"] This is the exact error message: [paste the error message, or write "there is no error message"] This is my complete plugin code: [paste your code] Find the cause and fix only that. Explain in one or two sentences what was wrong. Give me the complete file back.

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.

My WordPress plugin works. Now change one thing: [describe the change, for example: "show the reading time below the post instead of above it"] Keep everything else exactly the same. Give me the complete file back and tell me which lines you changed. This is my complete plugin code: [paste your code]

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?

Explain this WordPress plugin to me. I don't write code. For each part of the code: one sentence about what it does and when WordPress runs it. Then tell me which parts a visitor or another user can influence, for example by typing something into a form or changing the web address. Don't change the code. This is my complete plugin code: [paste your code]

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.

Run Plugin Check
  1. Go to Tools → Plugin Check and choose your plugin. Not under Tools? Plugins → Add Plugin, search for "Plugin Check", install, activate.
  2. 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!
  3. Pick one row, Error or Warning, whose Code contains Security, SettingSanitization, PreparedSQL or direct_file_access. More than one? Take an Error first. Copy that row.
Skip every other row today, even the Errors. Codes with 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.

Plugin Check gave me this result for a WordPress plugin I made with an AI. I don't write code, and there is no other developer: this is my own plugin. Explain in plain language what the problem is, who could trigger it (a visitor, a logged-in user, or only an admin like me), and whether it is a real risk on a small website. Don't fix anything yet. Plugin Check result: [paste the Plugin Check row] My complete plugin code: [paste your full plugin code]

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.

Fix only this issue in the plugin code below. Change as little as possible. Give me the complete file back, and list exactly which lines you changed and why. Don't add phpcs:ignore comments or anything else that hides the warning instead of fixing it. Only use functions that really exist in WordPress or PHP, and tell me the name of the function that does the fix, so I can look it up. Plugin Check result: [paste the Plugin Check row] My complete plugin code: [paste your full plugin code]

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.

What happened when we tried this loop (14 October 2026, with a small AI model running on a laptop. The free chatbots use bigger models and probably make fewer mistakes, so read this as what can go wrong, not what will.)

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.

You said you fixed this, but Plugin Check still shows it after I installed your new code: [paste the Plugin Check row] This is the code I installed: [paste your full plugin code] Explain why it is still flagged. If you think Plugin Check is wrong here, say so and explain why, but don't hide the warning. Then give me the complete corrected file.

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.

Review this WordPress plugin as a strict WordPress security reviewer. List every place where data from a user or the database is output without escaping, input is used without sanitising, or a form has no nonce. For each one, quote the line. If you find nothing, say so; don't invent problems. [paste your full plugin code]

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.

Wider track: paste your Round 1 prompt into a second AI tool and put the two results side by side. Which one is shorter? Which one gets fewer Plugin Check findings? Or pick a second idea from the ideas page.