Recipes

A recipe is a ready-made procedure for a job you do often: diagnose a problem, audit security, update plugins safely, check one page's SEO. Your AI app follows its numbered steps with PowerWP AI's tools. Every recipe that changes something looks first, shows you the exact texts, sets a checkpoint and ends with how to undo it.

The five packs#

PowerWP AI 1.6 ships 43 recipes in five packs. The packs that fit your site switch on by themselves.

A few recipes only appear where they apply. The WooCommerce recipes in the Every site pack need WooCommerce, and the Elementor recipes need Elementor. A general recipe steps aside when a more specific one is available: the WooCommerce check-up gives way to the digital and physical store check-ups.

Examples from the packs:

• Every site: Diagnose this site, Security audit, Performance review, Make a change safely, Before updating plugins, Monthly check-up, SEO check for one page, Fix a broken site, Set up the site memory.
• Physical goods store: Shipping store check-up, Low stock report, Find stuck orders, Update stock from a list.
• News, magazine or blog: Publish an article, Refresh an older article, Tidy categories and tags, Review the editorial queue.

The full list, with arguments and the permissions each recipe needs, is in the recipes reference.

Run a recipe#

AI apps show recipes as commands. Claude Code lists them as slash commands, for example /mcp__mystore__diagnose_site, where the middle part is the name of the server in your app. Apps that do not show commands can run a recipe through the tools recipes_list and recipe_get, so you can simply ask for it by name.

Example prompts:

Run the monthly check-up on my site.

Use the diagnose_site recipe. The symptom: the checkout page loads slowly.

Which recipes do you have for this site?

Some recipes take arguments, such as a threshold for the low stock report. Tell the app the values, or let it ask you.

How a recipe protects you#

A recipe that only reads says so and changes nothing. A recipe that changes something adds the same working style to its steps:

1. Look before changing anything.
2. Set a checkpoint with checkpoint_create, then use a dry run or a preview.
3. Show the exact new texts and wait for your approval.
4. Work in small batches.
5. Verify the result with page_check and error_log_read.
6. Finish with what changed, the change ids and how to undo it with changes_rollback.

If the connection lacks a needed permission, or the site is in read-only mode, the app does the reading steps, presents its plan and stops. Some actions cannot be rolled back; see What can't be undone.

Choose packs and switch recipes off#

Open PowerWP AI › Recipes. Under Recipe packs, Automatic uses the packs that fit your site. Choose lets you switch packs on and off yourself, and Detect again reads your site once more. Each recipe also has a switch that hides it from AI apps.

Adapt a recipe for your site#

Choose Adapt next to a built-in recipe to edit its steps. Your version is saved as this site's own, marked Your version, and it replaces the built-in one on this site. Plugin updates never change it. Choose Back to the built-in version to undo your edits.

In the editor you give the recipe a command name, a title and a description, write the numbered steps that name the tools to use, and add up to five arguments. Write {argument_name} where an argument's value goes. The Makes changes switch adds the working style above to your steps.

Save your own recipe#

After a task went well, tell your AI app:

Save what we just did as a recipe.

The app proposes the recipe with recipe_save. It waits for your approval under PowerWP AI › Recipes, like a memory entry. You can also choose New recipe and write one yourself. Do not put passwords, keys or customer data in a recipe. Recipe use is not reported to PowerWP.