Getting Started

Sharing Your Recipes

Published

When your AI agent makes your store cache-safe, it often writes recipes of its own: small fixes for plugins the recipe library does not cover yet. Sharing them with Super Speedy turns your store’s fixes into library recipes for every store, and once a recipe is in the library, we keep it up to date as the plugin changes.

Available since Cache Upgrader 1.7.13.

What you share

  • The recipes your agent wrote, from your “Cache Upgrader: Custom Cache Recipes” plugin.
  • Your agent’s chat log, or a summary of it. It tells us why each recipe exists, what was tried first, and what you decided. A summary is enough.
  • A short note, if you want to say anything to us.
  • The names and versions of your active plugins and theme, sent with every share so we can reproduce what the recipes handle.

Nothing you send is run or published as it is. Every recipe is reviewed by hand and rewritten as a generic library recipe before it reaches any other store.

Share from wp-admin

Open Super Speedy → Ajax and the Cache Upgrader tab, then scroll to Share with Super Speedy.

The Share with Super Speedy panel on the Cache Upgrader tab: site recipes ticked, a chat summary pasted, a file upload, a note, the consent box and the Share button
Tick the recipes to share, paste or upload your agent’s summary, agree, and press Share with Super Speedy.
  1. Recipes to share: every recipe your agent wrote is ticked. Untick any you would rather keep to yourself.
  2. Your AI agent’s chat log or summary: paste it, or upload a .md, .txt, .docx or .pdf file of up to 5 MB.
  3. A note for us: optional.
  4. Tick the consent box, then press Share with Super Speedy. The panel shows a reference; quote it if you write to us about the share.

Or ask your agent

Tell your agent “Share the recipes you wrote with Super Speedy, with a summary of what we did.” It asks you to confirm, then sends the recipes and its summary in one share and gives you the reference.

What to leave out

  • Passwords, API keys and licence keys. Remove any from a chat log before you share it.
  • Your customers’ personal details, such as names, email addresses or order details.

Your store’s address, product IDs and plugin settings are fine to leave in. We rewrite every recipe before it joins the library.

What happens next

  • We review what you sent. Recipes for plugins other stores use are rewritten as generic library recipes, tested, and released in a Cache Upgrader update.
  • Your store gets the library version the next time your agent fetches a build for your site. Once the library covers a plugin, your agent can switch on the library recipe and remove its own copy, so future fixes for that plugin come from us.

Further reading

what the recipes are, and where your site’s own recipes live.
setting the kit up on your store.

Written for Cache Upgrader for WooCommerce 1.7.13.

Fixing this on a real store?

Cache Upgrader Kit for WooCommerce does it for you.

Comments