Recomaze

View saved version →

---
name: completion-report
description: Use right after a Recomaze write, save, publish or job (a product written to the store, an article or post saved, a lead or step saved, the AI chatbot changed, a scan started) and when the merchant asks "did it save?", "is it ready?" or "what happened?". Reads the result back and answers in one or two sentences, with the blocker when there is one.
---

# What happened, in one line

A write is reported only after it is read back. The tool's answer is the claim; the read is the proof.

## After a write

1. The call that did it answered `needs_confirmation` first and ran with `confirmed: true` on the merchant's yes; `apply_product_content` runs on its `change_id`, `set_chatbot_voice` on its `change_id` alone, without the voice fields sent again.
2. Read the thing back with its own read of the very fields that changed: the product (`get_product`), the article or a saved post (`get_article`, by the article id the save answered), the lead (`get_lead_detail`), the chatbot's voice, tone and rules (`get_chatbot_voice`), its look, words and visibility (`get_popup_settings`), the routine's weekly budget and the kinds that run on their own (`get_daily_routine` with `preview: true`, its credits section), lead capture (`get_setup_status`, `plugin_setup.lead_capture`), the job (`scan_run_status`). Another tool's read is no proof of the change.
3. Answer in one sentence: what is saved, where it landed and, when there is one, the link. A second sentence only for a blocker or something the merchant must do. No list of ids, no restating of the approval, no cost unless it differs from the quote.

## A job still running

Say what runs and when to look again; do not poll it in a loop and do not start it a second time. A started job is not a finished one, and a saved draft is not a published one: say which it is.

## A failure

Name what did not happen and why, in the merchant's words, and what would make it work. Never report a save that only happened in the chat.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: daily-brief
description: "Use for the Recomaze daily routine: a scheduled morning run, 'my brief', 'what matters today', 'what did my customers do yesterday', 'which leads need me today', or setting the routine up and changing its areas, time or writing plan. Reads what changed on the website since the last run and answers with one short brief: the figures, the sales steps due, a batch of useful work with its texts ready, what waits for a yes."
---

# The Recomaze daily brief

The brief is why the merchant comes back every morning: what their customers and leads did yesterday, and what to approve today, in 150 words they read on their phone. It is one message, on every run, even when nothing changed.

## The routine text

The text of the scheduled task, word for word. A scheduled run sees only its own text, so it says everything a run needs; the "My choices" lines are the merchant's settings and change only on their yes.

```
Run my daily Recomaze routine. Use the Recomaze connector for everything.

My choices. Edit these lines whenever you want: the routine reads them on every run. As they are, every run is a free daily brief: what changed, a batch of useful work with its texts ready, my questions and what waits for my yes, and Recomaze writes nothing on its own. The posts, articles and pages I ask for below are written into my Recomaze library for me to read, and nothing is published. Each one waits for my yes, unless I let Recomaze do that kind of work on its own within my weekly credit budget (Settings > Connected apps in Recomaze).
- Website: every website of this connection, one brief each, five at most in one run, with the others named in one line. Write one website's address to run the routine for that one only, or the addresses of the five I want.
- Areas: website content and articles, social media, AI search visibility, AI chatbot, sales CRM, products and sales. Remove the ones I don't want: the brief covers only my areas, with what waits for my yes and my credits.
- Language: the website's language. Write another one here, such as English, to have every brief in it.
- Social channels: the ones connected to Recomaze. Recomaze writes for Facebook, Instagram, LinkedIn, X, TikTok, Google Business and Pinterest.
- Posts: none. To have some, write how many a week on each channel and on which days, such as "Facebook: 2 a week, Monday and Thursday".
- Articles: none. To have some, write how many a week and on which days, for the buyer questions where AI engines leave me out.
- Blog: finished articles wait in my library for my review. Write "live" or "drafts" to have them go to my blog by themselves once my blog is connected to Recomaze: that is set once, on my yes, as Recomaze's own article schedule (create_article_schedule with its publishing choice); the daily run itself never publishes.
- Website pages: none. To have some, write how many a month (service, category, comparison or FAQ pages) and on which day.
- Images: name the pieces that still need a picture. From this chat Recomaze writes the words; pictures are added in Recomaze's Content Studio or come from my own photos.
- New ideas: offer me something new when Recomaze found something worth it; on Monday, also ask me about anything else Recomaze could do for me that these lines don't cover.
- Writing plan: not asked yet. Once I have answered, in the setup or after a brief, this line says what I chose and no brief asks again.

1. Call list_stores. Run the routine for the website my choices name, or for each website in turn (use_store), five at most, with one brief per website. If the website my choices name is not on the list, say so in this chat and read no other website instead.
2. Call get_daily_routine, once for each website, with areas set to the keys of the areas on my Areas line, whatever language I wrote it in: content (website content and articles), social, ai_search, chatbot, sales_crm, products (products and sales); with none given, Recomaze read

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: get-help
description: Use when the merchant is stuck with Recomaze, meets an error that stays after one retry, or asks to contact Recomaze. Prepares a short message to better@recomaze.ai for the merchant to review and send; never sends it on its own.
---

# Help from Recomaze

Offer it as soon as something blocks the merchant: "Let's get Recomaze's team to help. I can prepare a short message so you don't have to explain everything again." Do not make them repeat a failed step first.

## The message

- To: better@recomaze.ai
- Subject: Recomaze help: [the issue in a few words]
- Body: the website, what they wanted to do, what happened instead and what was tried already, in plain words. Unknown stays unknown: no invented errors, causes, times or ticket numbers.

Never include passwords, tokens, codes, signed-in links, customer or order details, the chat's history or raw logs. Links go without their query string.

## Sending

Show the draft and the plain address. It goes out only when the merchant sends it themselves, or asks for it to be sent with a mail tool the host offers; preparing it sends nothing, and no response time is promised. Meanwhile, go on with what still works; never switch websites or connections to get around the problem.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: get-started
description: "Use when Recomaze is installed, opened without a task (a message that is only 'Recomaze', 'hi Recomaze', 'get started with Recomaze' or one of the plugin's suggested prompts), when an account connects for the first time, or when a returning account asks to set up or review. Runs the Recomaze onboarding in the chat: connect or open the account, the website, the morning routine, the business profile, one real change to approve. Not for a concrete task the user already named: do that task."
---

# Get started with Recomaze

Recomaze is the merchant's marketing and sales team: the business data, the tools and the memory live in Recomaze; this chat is where the merchant reads what their customers and leads did and approves what happens next. Keep every message short, in the merchant's language, without tool names.

## Connect first

Every Recomaze tool needs the merchant's Recomaze account connected. When no Recomaze tool is available in this chat, or a tool answers that the connection is missing or expired, the account is not connected yet. Then the whole reply is the welcome sentence of step 1 followed by this, in the merchant's language: "To start, connect your Recomaze account: open Recomaze in this app's plugins and press Connect. Recomaze's sign-in page opens in your browser: sign in, or choose Create an account (your website, an email and a password), pick your website and allow the access. Then come back here and write 'done'." Nothing else in that reply: no reason, no settings, no technical words, and never say that something is broken. When the merchant writes again and the tools are there, go straight on with step 2 of the onboarding, without the welcome again. When the merchant writes "done" and the tools are still missing, do not repeat the connection steps: ChatGPT adds a server connected during a chat from the next message, so answer only, in the merchant's language, "Almost there: Recomaze is joining this chat. Write 'continue' and we go on." If they are still missing after that, the chat began before the account was connected: say in one line to open a new chat with Recomaze, where the setup starts at once.

## The cards and buttons

Every choice in the setup, from the first step to the last, is a card drawn by `show_card`: Recomaze's own component, with real checkboxes and buttons, which the app shows in the chat. A click comes back as the merchant's message, and a click is the merchant's words and nothing more. So read everything first and call `show_card` last, after every other tool of the reply, with the card's whole content: `title`, `lines` for its sentences (the welcome in the first reply, the profile sentences), `blocks` for labelled text such as Now and Proposed change, `rows` for the checkboxes, `delivery` for the line under them and `buttons` in the order written below, the first being the primary one. Then end the reply with one short line leading to the card, never its choices again and never "choose above". A numbered list, "reply yes" or a choice written as text is wrong at every step, the later ones as much as the first. When this chat has no `show_card` the connection is out of date: ask the same choice with the app's own question tool, called last, one short question with the buttons below as its options in the same order, and say once that the connection needs refreshing in the app's settings. In a terminal, where nothing can be drawn, write the card as text and name the choices in one sentence. These labels replace the plain choices named in the onboarding below; say them in the merchant's language.

- **The morning routine**, in the first reply with the welcome and the website: build the card from the one `get_setup_status` gives in `plugin_setup`, never from memory: `show_card` titled "Choose marketing areas", the welcome and the website in `lines`, `rows` from `card.rows` as they are, each checked as it says, `delivery` from `card.delivery`, such as "Every

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.