AI assistant · N5 Complete system
Carousel Tool Creator for Restaurants
With the Universal Carousel Engine folder, your AI builds YOUR restaurant's carousel factory, part by part and checking each one: first the verdict on whether it pays, then the house configuration, the topic layer, the guardian's rules and the two fixed slides as files, and finally the render, the batch, verified publishing and measurement.
N5Complete system
Several chained pieces you install and operate over time, with their review cadence. It changes how the business runs, not one decision.
◆ This assistant 117 of the 170 published assistants are at this levelIs this for you?
What it does and what you get
- A carousel engine is not bought ready-made nor written from scratch: the hard part —that the same table always yields the same pieces, that a guardian bounces weak copy before anything is drawn, that the batch does not fail on publishing, that what is published gets measured— is already solved and measured inside the Universal Carousel Engine folder, with its specification in twelve documents and its templates.
- What no universal folder can bring is what YOUR house talks about, in which words and with which prohibitions.
- This assistant has your AI, with that folder, build the tool in the right order: first it tells you with figures whether it pays —because a tool that does not pay gets switched off in two months—, then it writes your house's files (configuration, topic layer, guardian rules with numeric thresholds) and only then raises the factory part by part, telling you which command checks each one.
- Anything you have not told it stays marked as PENDING, never filler: an invented slide about your business will be read by a customer of yours.
What you end up with
The verdict with your figures and the sentence on whether it pays; configuracion.json with your house's data and PENDING items marked, without a single credential holding a value; the topic layer in temas_familias.json with the consumption reason each piece aims at; the guardian rules in guardian_reglas.json with numeric thresholds and your banned-phrase list; your brand's two fixed slides written once; the factory built part by part —render, batch of the first 8 pieces, guardian, verified publishing and measurement— with the command that checks each one; and the switch-on order with owner, indicator with target and baseline, and the sixty-day switch-off rule.
EXAMPLE This is what you getAn example built with Sazón de Origen, one of the house's fictional businesses.Not your data: your result is built with YOUR restaurant's.See the full example →Sample result
The owner asked this: «We publish about three carousels a month, and only when I remember. An outside designer makes them and charges me $90,000 each. I know we should publish more but there are not enough hours.»
| Pieces per month today | 3 |
| Cost per piece | $90,000 |
| Current monthly spend | $270,000 |
| Pieces per month with the factory | 20 |
| Engine's monthly cost (storage + publishing + model) | ~$120,000 |
| Cost per piece with the factory | ~$6,000 |
It pays for itself in the first batch, and not because of what it saves: because of the seventeen pieces that do not exist today. Warning: the engine cost assumes twenty pieces a month — if you publish five, the saving per piece drops and the sum still works, but by less.
| Topic | Consumption reason | Dish of the mix | Moment in the month | Datum needed |
|---|---|---|---|---|
| Why the bandeja has been the same for 30 years | weekend with family | Bandeja Paisa · star | week 1 | the year the recipe was fixed |
| What nobody sees in a properly made chicharrón | sharing with family | Chicharrón · workhorse | week 2 | hours of process |
| The car park that decides Sunday | families with children | none · pushes occupancy | week 3 | PENDING: how many spaces |
Split for the month: 60% to what holds the margin, 40% to what needs to become known.
| Rule | Threshold | Why |
|---|---|---|
| Cover headline | 42–68 characters | below it says nothing; above it gets cut on mobile |
| Figures per piece | minimum 1 | a piece without a number is an opinion |
| Sameness between consecutive slides | max 60% | two slides saying the same thing waste a slide |
| Forbidden phrases | 9 | written from your tone, not mine |
It travels as DATA in `guardian_reglas.json`, with the shape of the folder's template: changing a threshold does not touch a line of code.
Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.
This is 3 of 4 parts. Behind the wall are **configuracion.json and the two fixed slides written out**, **the factory built part by part with the command that checks each one** and **the switch-on with owner, indicator and sixty-day switch-off rule**.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 13 of the 24 fields in «My Restaurant», among them Restaurant name, Business type and Cuisine or concept. It does not ask out of curiosity: these are what make the answer speak about YOUR scale instead of an industry average — the same calculation on a business of another size returns a number you cannot decide with.
You fill them once and they apply across the library, so the second assistant you open already starts with them in place. Whatever you leave blank, the assistant asks for one thing at a time instead of inventing it, and says so before answering, so you know what it is working from.
Always up to date
Every assistant carries a visible version and date. When an AI changes how it works, the assistant's version goes up and you see what changed.
v2.0.02026-10-08Renamed from «Carousel Engine Implanter» to «Carousel Tool Creator» (Diego's decision, 2026-10-08: creators that deliver a house engine's universal folder share one naming, docs/72) and its body is rewritten with what package 1.26.67 brings: it used to write the copy and rules so ANOTHER AI would build the factory; now it has the AI, with the folder, write the house files (configuracion.json, temas_familias.json, guardian_reglas.json) in the shape of its templates and raise the factory part by part —render, batch, guardian, verified publishing, measurement and planning (docs/10 and 11)— stating the command that checks each one, without writing outside the folder (docs/12). The kit travels whole, with its verifier, and passes the house privacy veto. Same slug and address.v1.0.02026-09-03Initial version. Commissioned by Diego F. Parra on 2026-09-03: «I do not see the prompt for the carousel tool builder based on the universal carousel engine». Measured that day: it did not exist —the catalogue only had the Complete Carousels Builder (MPV-1123), which writes carousels and whose form is `guion`, not the tool that manufactures them—. Born together with the Universal Carousel Engine downloadable kit (26 files, 304 KB, distilled from version 1.0.0 of the origin engine), served through the same plan-gated door as the other kits, and with the three folders: Universal Kit, Visual Kit and its own. It is called Implanter and not Builder per doc 35 §3: the universal already exists and this prompt makes it THIS restaurant's.More assistants in this category
Not one cycle: the whole ring. Which decisions your house takes today without a figure, which cycles feed them…
N5 · Complete systemThe board of boards: the census of the cells you fill by hand, which ones can fill THEMSELVES with what you al…
N5 · Complete systemYou bring a routine you already do by hand —reviewing the month's numbers, tidying up what came out of the mee…
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.
