先认一遍三块屏幕，再看数据放在哪里。

数据放在哪里

运行时（sync-prompts、生成流程）从来不读第 ① 层的草稿，它只认 Airtable 里的普通文字。所以在这个工具里怎么拆格子、用不用变量，都不影响线上，直到你推送并 Publish。

页面会自己把 Airtable 里现有的 prompt 导进来，你不用建任何东西。

1. 1在首页点 04 Prompt 助手（登录后才会出现）。第一次打开会弹出导览，也可以随时点顶部的 导览 重看。
2. 2页面把 Prompt Manager 里所有 prompt 读进来，逐行导入成模板，顶部提示「已从 Airtable 导入 N 个 prompt」，同时把「源」存进 Supabase。导入只读 Airtable，不会改它。
3. 3导入是逐字的：不能按「# 标题」拆成格子的字段，会整段放进一格（头部有提示条说明），推送出去的内容和 Airtable 里的一字不差。
4. 4左边列表按 Marketplace 分组，生产在前，测试模板缩进在它派生自的生产模板下面。每一项的圆点是状态：
   已和 Airtable 同步 · 有未推送的改动 · Airtable 里被别人改过 · 未推送（新建）· Airtable 里已没有这一行。
5. 5别人在 Airtable 里改了或新加了行？点左下角 刷新 Airtable 重新读一遍；想把和 Airtable 不一样的 prompt 一次拉回来，点旁边的 从 Airtable 拉取（会先重新读 Airtable、列出清单让你勾选；有你没推送的改动的会标出来，拉取后可以 Ctrl+Z 撤销）。页面还会每 45 秒、以及你切回这个标签页时，自动检查别人在 Supabase 里保存的新版本（只查 Supabase，不会读 Airtable）。

一个很长的字段 = 若干格。每格单独改，推送时按顺序拼回去。

1. 1点格子的标题栏展开它。标题就是字段里「# 标题」那一行，下面是它的正文。
2. 2标题栏右边的开关决定这一格进不进推送内容：停用的格子不会推到 Airtable。↑ ↓（或拖动最左边的点点）调顺序，也可以复制、删除（删除要点两次确认）。
3. 3每个位置的底部有 添加一格 和 从其它模板复制一格…。后者可以多选，也可以按模板整批勾；格子里的变量会按来源模板展开成当前的值，所以复制过来的是完整的文字。每格底部的 从其它模板替换… 是整格替换。
4. 4没动过的格子推送出去一字不差：每格都记着自己前后的空白，拼回去和原来的字段一模一样。
5. 5头部的 Scope 选这个 prompt 适用于哪些类目：All categories 是兜底，具体的 Category / Item Type 优先于它。1 call / 2 calls 可以随时切换。
6. 6撤销 / 重做：在文本框外面按 Ctrl+Z 撤销上一步改动（挪格子、删格子、开关、联动、改共享块……），Ctrl+Shift+Z 或 Ctrl+Y 重做；一次连续打字算一步。在文本框里按 Ctrl+Z 是浏览器自己撤销打的字。最多记 80 步；新建、Fork、删除整个 prompt 或重新载入之后，历史清空。推送、Publish 这类写进 Airtable 的操作撤销不了。

一个 prompt 有哪些位置

1 call 的 prompt 只有一页，所有位置（包括 Validation Rules）都在这一页上；Call 2 的内容留着，切回 2 calls 就找回来。

⟦ ⟧ 是这个工具自己的变量。页面里还有别的花括号，别混。

变量有哪几种

1. 1在格子底部 插入变量… 里选一个，插在光标处。预览里变量显示成它现在的值，例如 830–1300。
2. 2变量没定义时（比如对应的字段被删了），这一格会标「变量未定义」，检查里也会报，推送出去会是字面的 ⟦…⟧，所以要修好再推。
3. 3想把变量变回普通文字：「字段与长度」里的 全部展开成文字。推送出去的永远是展开后的文字，所以这一步不会改变 Airtable 里的内容，只是以后改一个数不再带动另外两处。

一个字段的要求同时写在三个地方：System Prompt 的文字、Output Schema、Validation Rules。「字段与长度」这一节把它们连起来：改一处，另外两处跟着变。

新字段：在 System Prompt 里诞生

• 在 System Prompt 某一格的字段清单里新写一个名字，离开这一格时它会自动补进 Output Schema（提示条里可以撤销；「自动补全」勾选框可以关）。
• 或者点格子底部的 新字段…：填字段名、类型（文本 / 文本列表 / 对象）、字符数或条数、是否必填。确认后一次加完：Output Schema、Validation Rules（只写校验代码读得到的键）、这一格里的说明（长度用变量）；两段式还可以顺便让 Call 2 引用它。
• Output Schema 里有、System Prompt 里没人讲的字段，会标「没有对应的格子」，点 新建格子 生成一格。

字段表

• 每个顶层字段 ↔ 讲它的那一格 ↔ Validation Rules 里有没有它的键。「必填」勾选框对应 Schema 的 required。
• 改名（铅笔）和删除（垃圾桶）会让 Schema、校验、文字里的变量、格子的对应关系一起改；文字里直接写的字段名会列出来，由你勾选要不要一起改。
• 字段有固定的可选值（枚举）时，Output Schema 区的「可选值」里每个值是一个小标签：＋ 新值，回车 加一个，铅笔改名，× 删掉。Schema 和文字里的 ⟦enum:…⟧ 清单一起变；改名时文字里直接写着旧值的地方会列出来，由你勾选要不要一起改。删值时不会动文字里直接写的，只告诉你还有几处。都可以 Ctrl+Z。
• 想在一处管全部字段：左下角 字段管理（在共享库上面）。它列出这个 prompt（Call 1 / Call 2 分页）的每个字段：必填勾选、铅笔改名、垃圾桶删除、可选值标签（加 / 改名 / 删），以及 添加字段。从这里点开的改名、删除、添加字段对话框，做完或取消后都会回到字段管理。

长度 / 条数

• 页面从文字、Schema、校验里认出「830–1300 字符」「5 条」这样的要求，列成一张表：每项在哪几处出现、值是多少。写得不一致的标 对不上。
• 点 联动（或 联动全部可联动项）：写死的数字换成 ⟦limit:…⟧，几处共用同一个值。之后在表里改这个数，几处一起变。联动前会让你看清楚会改哪里；几处写的值不一样时，要你选采用哪一个。
• 校验代码只读特定的键（min/max_chars、min/max_words、exact_items、item_min/max_chars、total_min/max_chars 等）；写了别的键不会生效，表里会标「不生效」。

Call 1 的输出 → Call 2

• 只在两段式里有。Call 2 看不到原始产品数据，只靠 Call 1 的输出。Call 2 页的「字段与长度」里有一张表：Call 1 的每个字段，Call 2 的 System Prompt 用到了吗（已联动 / 提到 / 没用到）。
• 让 Call 2 引用… 选字段和要加进哪一格，会在那一格末尾加一句 Use the approved ⟦in:字段⟧ from the content plan.
• 用引用 ⟦in:…⟧ 而不是直接写字段名：Call 1 里改名或删除，Call 2 的文字跟着变，不会悬空。Call 2 提到了 Call 1 没有的字段，会提示 在 Call 1 里新增。

一处改，处处变：多个 prompt 共用同一段文字。

1. 1共享块 = 只存一份的文字，被很多 prompt 的格子引用，在格子里写作 ⟦@call1·system_prompt·role·wayfair⟧（命名：调用·位置·格子·范围）。
2. 2范围有两种，对任何格子都可用：
   整个 Marketplace：这个 marketplace 下的生产、测试、各 Scope 的行都能用，常用于 System Prompt 里讲这个 marketplace 自己规则的格子；
   分组：你自己挑的一组 prompt，可以跨 Marketplace，常用于所有 marketplace 都一样的内容，比如 Optimization preferences。
3. 3创建：在格子底部点 设为共享块…，选范围、看名字、勾选哪些 prompt 里的同名格子一起换成引用。也可以去左下 共享库 的「建议」页，工具会在那里列出「一字不差、却各存一份」的格子。
4. 4引用共享块的格子，上面有一条提示：范围、被 N 个 prompt 使用（附名单）。在这一格里改，名单上所有 prompt 一起变。断开成本地副本 让这一格变回普通文字，不再影响别的 prompt。
5. 5共享块改了，用到它的 prompt 都会变成「有未推送的改动」。共享库里有 把受影响的 N 个一起推到 Airtable（点两次确认）：只推，不 Publish；有错误、被别人在 Airtable 里改过、有冲突、缺 Marketplace 选项的会跳过，并列出原因。
6. 6一键应用：选中一个共享块，下面会列出范围内（这个 marketplace，或这个分组）还没用上它的 prompt，每个标着：文字一致（直接换成引用）、文字不一样（会被共享块覆盖，可以先看差异）、没有这一格（新加一格）、已是别的共享块（不动）。勾选后点 应用到所选。默认只勾「文字一致」和「没有这一格」的，不会覆盖你写过的不同文字。
7. 7分组页里每个分组有 把共享块应用到全部成员：这个分组的每个共享块，一次放进每个成员，同样只动「文字一致」和「没有这一格」的，其余的数一下告诉你。给分组加了新成员之后用它最方便。
8. 8Output Schema 也能共享：Output Schema 区的 设为共享块… 把整份 Schema 放进共享库，别的 prompt 用 改用共享块… 换上同一份。之后在任何一个 prompt 里改字段（加、改名、删、必填）或直接改 JSON，改的都是共享的这一份，用到它的 prompt 一起变；但它们各自的 System Prompt、Validation Rules 里的字段名要自己跟上，检查会提示。「联动」不会改共享 Schema 里的数字，要在共享的 JSON 里直接写 ⟦limit:…⟧。断开成本地副本 让这个 prompt 用回自己的一份。

右边三个页签，改的时候随时看。

预览

模型实际收到的内容：System、User 和 Response format（OpenAI json_schema），附字符数和大约的 token 数。变量已经换成现在的值；点任意一段，跳到对应的格子；两段式可以切 Call 1 / Call 2；「显示格子边界」把每格的范围标出来。

检查

列出所有可能出错的地方，按严重程度分三级，每条带「定位」，能自动修的带修复按钮：

对比

我的版本和 Airtable 现状逐行对比；测试模板还能切换成和它派生自的生产模板对比。别人在 Airtable 里直接改过的内容会在这里提醒你，可以 拉回 Airtable 的版本（放弃我没推送的改动），或 保留我的，下次推送覆盖。

草稿存在 Supabase，两个人同时改不会悄悄互相覆盖。

1. 1头部的小条（源已存 Supabase · rev N）显示草稿的保存状态：已保存 / 未保存（自动保存中）/ Supabase 有新版本 / 源有冲突。点它打开「数据存在哪里」。
2. 2改完停下来约 1 秒自动保存。可以在弹窗里关掉自动保存，改成手动。保存失败会提示原因，并可重试。
3. 3每份文档（prompt、共享块、分组）同时有三份：Supabase 现在的、这个页面上次载入或保存的、屏幕上的。只有我改了 → 「还没保存」；只有别人改了 → 「新版本」，点 拉取；两边都改了 → 冲突，不会覆盖，要你选 拉取（放弃我的） 还是 以我的为准。
4. 4别人新建的 prompt、共享块、分组，下次检查时会自动出现在你的列表里。

存什么：每个 prompt 的源（格子、变量、长度值、Schema 原文、上次同步 Airtable 时的文字快照）、共享块、分组。不存：拼装结果、检查、预览、对比（都是页面里现算的）；Airtable 里的展开文字（它属于 Airtable）；已发布的版本历史（仍然只由 sync-prompts 写）。

推送 = 把展开后的文字写进 Airtable。Publish 是另一件事，默认不做。

1. 1点头部右上的 推到 Airtable。页面先重新读一遍 Airtable 上这一行（看有没有被别人改过），再给你一张确认页。
2. 2确认页告诉你：
   · 写入什么：新建一行（Prompt Code 由 Airtable 分配），或更新 #N 行，并列出有改动的字段。变量先展开成最终文字。只写 Prompt Manager 的输入字段，Live Status / Live Info 这些由 sync-prompts 写的字段不会碰。
   · Marketplace 选项（Prompt Manager / Generation Items / Batches 三张表）有没有；
   · 检查：有错误不能推，警告不拦；
   · 源：推送前会先把没保存的存进 Supabase；有别人的新版本会先拦住；
   · Airtable 上被人改过：要勾「我知道会覆盖」，或先 拉回 Airtable 的改动。
3. 3Publish = 勾上这一行的 Publish，运行 sync-prompts，再读回 Live Info 核对。生产 marketplace 默认只写 Airtable，勾 Publish 还要输入 marketplace 名字再确认一次；测试 marketplace 默认一步到位。sync-prompts 会发布这个 marketplace 里所有勾着 Publish 的行。如果别的行也勾着，会先拦住并列出名单，让对应的人处理。
4. 4新的 Marketplace 选项：Prompt Manager 里的选项会在写这一行时自动创建，前提是后台配置了 AIRTABLE_SCHEMA_TOKEN。没配的话，要先在 Airtable 里手动加一次（任意一格输入新值，选 Create），缺选项时不能推送。Generation Items / Batches 里的选项靠「临时写一条记录再删掉」来建，要在确认页勾选。

不动生产，先在测试 marketplace 里试。

1. 1在生产 prompt 上点 Fork 成测试，起个后缀（如 test0930 或你的名字）。测试的 Marketplace 是「原名-后缀」。它复制所有格子和设置；共享块默认变成各自的本地文字，改测试不会影响生产（勾「测试副本继续共享这些块」才继续共享，那样在测试里改共享块会连生产一起改）。
2. 2Fork 本身不碰 Airtable。第一次推送这个测试 prompt 时，才会在 Prompt Manager 新建一行（有权限的话顺带创建 Marketplace 选项）。
3. 3试：在 Listing Generator 里 Marketplace 选「Other…」，输入这个测试名，就会用测试 prompt 生成。
4. 4做好了，在测试 prompt 上点 合回生产：列出它和生产模板的差异，勾选要搬回去的改动，应用到生产模板。这只改工具里的生产模板；Airtable 里的生产那一行还没动。要让它生效，到生产模板里「推到 Airtable」，需要的话再 Publish。

新建

左上 新建：① 从哪里开始：任何一个现有模板，或空白；② 分类：Marketplace（或新 Marketplace）、环境（生产 / 测试，测试要填后缀）、1 / 2 calls、Scope、Prompt Name。从另一个 marketplace 的模板复制时，可以勾选把文字里的 marketplace 名一起换掉。

新建的 prompt 在第一次推送之前只存在 Supabase 里（草稿）；第一次推送才会在 Airtable 新建一行。新 Marketplace 先作为自定义名使用（和 Listing Generator 的「Other…」一样）；要成为正式 marketplace，还需要开发者把它加进 supabase/functions/_shared/marketplaces.ts。

删除：先停用，再确认两次

1. 1先停用（retire）：如果这个 prompt 在 Supabase 里有线上版本，Scope 改成 REMOVE — retire this prompt (no new version)，只写 Airtable 的 Scope 和 Publish 两个字段，sync-prompts 认出后把线上版本变成 RETIRED（历史保留）。生产 marketplace 要输入 marketplace 名字确认。没有线上版本就不需要这一步。
2. 2第一次确认：看清单、勾选。会删：Airtable 里这一行、Supabase 里这个 prompt 的源。不会删：已发布过的历史版本（RETIRED，留作记录）；它用到的共享块；派生出的测试副本（只是失去「派生自」）。会提示删完后哪些 Scope 没有 prompt 了。All categories 是兜底，没了它，没有更具体 prompt 命中的产品会生成失败。
3. 3第二次确认：输入这个 prompt 的名字，点 永久删除。

如果 Airtable 里的行被别人删了，列表里会标「Airtable 里已没有这一行」：再推送会新建一行（Prompt Code 换成新的），或点 不要了，删掉这个 prompt…。

First get to know the three panes, then see where the data lives.

Where the data lives

The runtime (sync-prompts, the generation flow) never reads the draft in layer ①; it only knows the plain text in Airtable. So how you cut cells or whether you use variables in this tool does not affect production until you push and Publish.

The page imports the prompts that are already in Airtable by itself; you do not have to create anything.

1. 1On the home page click 04 Prompt Assistant (it only appears after you sign in with an admin account). The first time, a tour pops up; you can replay it any time with Tour at the top.
2. 2The page reads every prompt in the Prompt Manager and imports it row by row as a prompt; a message at the top says “Imported N prompts from Airtable”, and the “source” is saved to Supabase. Importing only reads Airtable; it never changes it.
3. 3Importing is word for word: a field that cannot be cut into cells at its “# heading” lines without changing it is kept whole in one cell (a bar at the top says so), so what is pushed is identical to Airtable, character for character.
4. 4The list on the left is grouped by Marketplace, production first, with a test prompt indented under the production prompt it was forked from. The dot on each item is its state:
   In sync with Airtable · Unpushed changes · Changed in Airtable · Not pushed yet (new) · No longer in Airtable.
5. 5Did someone change or add a row in Airtable? Click Refresh Airtable at the bottom left to read it again. To bring every prompt that differs from Airtable back in one go, click Pull from Airtable next to it (it reads Airtable again and lists the prompts for you to tick; ones with changes you have not pushed are marked, and Ctrl+Z undoes a pull). The page also checks for newer versions that others saved in Supabase every 45 seconds and whenever you switch back to this tab (it only asks Supabase; it does not read Airtable).

One very long field = several cells. Edit each cell on its own; a push joins them back in order.

1. 1Click the title bar of a cell to open it. The title is the “# heading” line of the field, and below it is its text.
2. 2The switch on the right of the title bar decides whether the cell goes into the push: a cell that is turned off is not pushed to Airtable. ↑ ↓ (or drag the dots on the far left) change the order; you can also duplicate and delete (delete asks for a second click).
3. 3Each part has Add a cell and Copy a cell from another prompt… at the bottom. The latter allows several picks, or ticking a whole prompt at once; the variables in a cell are expanded with the source prompt's current values, so what is copied is complete text. Replace from another prompt… at the bottom of each cell replaces the whole cell.
4. 4A cell you did not touch is pushed byte for byte: each cell remembers the whitespace before and after it, so joined back it is exactly the original field.
5. 5Scope in the header chooses which categories the prompt applies to: All categories is the catch-all, and a specific Category / Item Type wins over it. 1 call / 2 calls can be switched at any time.
6. 6Undo / redo: outside a text box press Ctrl+Z to undo the last change (moving a cell, deleting, the switch, linking, editing a shared block…) and Ctrl+Shift+Z or Ctrl+Y to redo; one stretch of typing counts as one step. Inside a text box Ctrl+Z is the browser undoing your typing. It remembers up to 80 steps; the history is cleared after New, Fork, deleting a whole prompt or reloading. What writes to Airtable, such as a push or Publish, cannot be undone.

The parts of a prompt

A 1-call prompt has just one page with every part on it (Validation Rules included); Call 2's content is kept, and switching back to 2 calls brings it back.

⟦ ⟧ are this tool's own variables. The page has other curly braces too; do not mix them up.

Kinds of variable

1. 1Pick one under Insert variable… at the bottom of a cell; it goes in at the cursor. In the preview a variable shows its current value, for example 830–1300.
2. 2When a variable is not defined (say its field was deleted), the cell is marked “Variable undefined”, the checks report it too, and it would go out as a literal ⟦…⟧, so fix it before pushing.
3. 3To turn variables back into plain text: Turn all into text under “Fields and lengths”. What is pushed is always the expanded text, so this does not change Airtable; it only means that changing one number later no longer carries over to the other two places.

What a field must look like is written in three places at once: the System Prompt text, the Output Schema and the Validation Rules. The “Fields and lengths” section ties them together: change one and the other two follow.

A new field: born in the System Prompt

• Write a new name in the field list of a System Prompt cell and, when you leave the cell, it is added to the Output Schema by itself (you can undo it in the hint bar; the “Auto-complete” tick box can turn it off).
• Or click New field… at the bottom of a cell: give the field name, type (text / text list / object), characters or items, and whether it is required. On confirming, everything is added at once: the Output Schema, the Validation Rules (only keys the validation code reads), and a description in this cell (lengths as variables); in a two-call prompt you can also have Call 2 reference it.
• A field that is in the Output Schema but that no System Prompt cell talks about is marked “no matching cell”; click Create the cell to make one.

The field table

• Every top-level field ↔ the cell that talks about it ↔ whether Validation Rules has a key for it. The “Required” tick box is the Schema's required.
• Renaming (pencil) and deleting (bin) change the Schema, the Validation, the variables in the text and the cell links together; field names written directly in the text are listed and you tick whether to change them too.
• When a field has fixed allowed values (an enum), each value under “Allowed values” in the Output Schema section is a small tag: + new value, Enter adds one, the pencil renames, × deletes. The Schema and the ⟦enum:…⟧ lists in the text change together; when renaming, the places in the text that write the old value directly are listed and you tick whether to change them too. Deleting a value does not touch what is written directly in the text; it only tells you how many places remain. All of it can be undone with Ctrl+Z.
• To manage all fields in one place: Field manager at the bottom left (above the shared library). It lists every field of this prompt (Call 1 / Call 2 on separate pages): required tick, pencil to rename, bin to delete, allowed-value tags (add / rename / delete), and Add a field. The rename, delete and add-a-field dialogs opened from there come back to the field manager when done or cancelled.

Lengths / counts

• The page recognises requirements such as “830–1300 characters” or “5 items” in the text, the Schema and the Validation and lists them in a table: where each appears and what its value is. Ones written differently are marked Mismatch.
• Click Link (or Link everything that can be linked): the hard-coded numbers are replaced with ⟦limit:…⟧ and share one value. After that, change the number in the table and all the places change. Before linking you are shown what will change; when the places hold different values, you choose which one to use.
• The validation code only reads certain keys (min/max_chars, min/max_words, exact_items, item_min/max_chars, total_min/max_chars and so on); any other key has no effect, and the table marks it “no effect”.

Call 1's output → Call 2

• Only in a two-call prompt. Call 2 cannot see the raw product data, only Call 1's output. “Fields and lengths” on the Call 2 page has a table: every Call 1 field, and does the Call 2 System Prompt use it (linked / mentioned / not used).
• Make Call 2 use it…: choose the field and the cell to add it to; a sentence Use the approved ⟦in:field⟧ from the content plan. is added at the end of that cell.
• Use the reference ⟦in:…⟧ rather than writing the field name: rename or delete the field in Call 1 and Call 2's text follows; nothing dangles. If Call 2 mentions a field Call 1 does not have, you are offered Add it to Call 1.

Edit once, change everywhere: many prompts share one text.

1. 1A shared block = one stored text that cells in many prompts reference; in a cell it is written ⟦@call1·system_prompt·role·wayfair⟧ (naming: call·position·cell·scope).
2. 2There are two kinds of scope, and both work for any cell:
   The whole Marketplace: every production, test and per-Scope row under this marketplace can use it; usually for System Prompt cells that state this marketplace's own rules;
   A group: a set of prompts you pick yourself, which may span marketplaces; usually for content that is the same in every marketplace, such as Optimization preferences.
3. 3To create one: click Make a shared block… at the bottom of a cell, choose the scope, look at the name, and tick which prompts' same-name cells are swapped for the reference. You can also go to the “Suggestions” page of Shared library at the bottom left, where the tool lists cells that are “word-for-word identical yet stored separately”.
4. 4A cell that references a shared block has a bar on top: the scope, and used by N prompts (with the list). Edit it in this cell and every prompt on the list changes. Detach into a local copy turns the cell back into plain text that no longer affects other prompts.
5. 5When a shared block is edited, every prompt that uses it shows “Unpushed changes”. The shared library has Push the N affected to Airtable together (click twice to confirm): it only pushes, it does not Publish; prompts with errors, changed in Airtable, in conflict or missing the Marketplace option are skipped, with the reason listed.
6. 6One-click apply: select a shared block and below it lists the prompts in its scope (this marketplace, or this group) that do not use it yet, each marked: same text (swapped straight for the reference), different text (will be overwritten by the shared block; look at the difference first), no such cell (a cell is added), already another shared block (left alone). Tick some and click Apply to the selected. By default only “same text” and “no such cell” are ticked, so different text you wrote is never overwritten.
7. 7On the Groups page every group has Apply the shared blocks to all members: every shared block of the group goes into every member in one go, again only where the text is the same or the cell is missing, and the rest is counted and reported. It is handiest after adding a new member to a group.
8. 8The Output Schema can be shared too: Make a shared block… in the Output Schema section puts the whole Schema in the shared library, and other prompts switch to the same one with Use a shared block…. After that, changing a field in any prompt (add, rename, delete, required) or editing the JSON changes the one shared copy and every prompt that uses it; but the field names in each prompt's own System Prompt and Validation Rules have to be followed up by hand, and the checks will say. “Link” does not change numbers in a shared Schema; write ⟦limit:…⟧ straight into the shared JSON. Detach into a local copy makes this prompt use its own copy again.

Three tabs on the right; look at them while you edit.

Preview

What the model really receives: System, User and the Response format (OpenAI json_schema), with the character count and an approximate token count. Variables show their current values; click any part to jump to its cell; a two-call prompt can switch between Call 1 / Call 2; “Show cell boundaries” marks where each cell starts and ends.

Checks

Everything that could be wrong, in three levels of severity; each has “Go to it”, and a fix button where it can be fixed automatically:

Diff

My version against what Airtable holds now, line by line; a test prompt can also be switched to compare with the production prompt it was forked from. Edits someone made straight in Airtable show up here, and you can Pull in the Airtable version (dropping my unpushed changes) or Keep mine; the next push overwrites it.

Drafts are stored in Supabase, so two people editing at once never silently overwrite each other.

1. 1The small bar in the header (Source saved in Supabase · rev N) shows the draft's save state: saved / unsaved (autosaving) / newer version in Supabase / source conflict. Click it to open “Where the data lives”.
2. 2About a second after you stop editing it saves by itself. You can turn autosave off in the dialog and save by hand. A failed save says why, and can be retried.
3. 3Every document (a prompt, a shared block, a group) exists in three copies at once: the one in Supabase now, the one this page last loaded or saved, and the one on screen. Only I changed it → “not saved yet”; only someone else changed it → “newer version”, click Pull; both changed it → conflict, nothing is overwritten, and you choose Pull (drop mine) or Keep mine.
4. 4Prompts, shared blocks and groups that others create appear in your list by themselves the next time it checks.

What is stored: each prompt's source (cells, variables, length values, the raw Schema, a snapshot of the text as of the last Airtable sync), shared blocks and groups. Not stored: assembled results, checks, previews and diffs (all computed in the page); the expanded text in Airtable (it belongs to Airtable); the history of published versions (still written only by sync-prompts).

A push = writing the expanded text into Airtable. Publish is a separate thing and is off by default.

1. 1Click Push to Airtable at the top right of the header. The page first reads this row in Airtable again (to see whether someone changed it) and then shows a confirmation page.
2. 2The confirmation page tells you:
   · What will be written: a new row (Airtable assigns the Prompt Code), or an update of row #N, with the changed fields listed. Variables are expanded into the final text first. Only the input fields of the Prompt Manager are written; fields written by sync-prompts, such as Live Status / Live Info, are not touched.
   · Whether the Marketplace option exists (in the Prompt Manager / Generation Items / Batches tables);
   · Checks: errors block the push, warnings do not;
   · Source: anything unsaved is saved to Supabase first; if someone else has a newer version it stops;
   · Changed in Airtable: tick “I know this overwrites” or first Pull in the Airtable changes first.
3. 3Publish = tick Publish on the row, run sync-prompts and read Live Info back to verify. A production marketplace by default only writes Airtable; ticking Publish also asks you to type the marketplace name to confirm; a test marketplace does it in one step by default. sync-prompts publishes every row in the marketplace that has Publish ticked; if other rows are ticked too, it stops first and lists them so their owners can deal with it.
4. 4A new Marketplace option: the one in the Prompt Manager is created automatically when the row is written, provided the back end has AIRTABLE_SCHEMA_TOKEN configured. If not, add it by hand in Airtable once (type the new value into any cell and choose Create); a push is not possible while the option is missing. Options in Generation Items / Batches are made by “writing a temporary record and deleting it”, which you tick on the confirmation page.

Do not touch production; try it in a test marketplace first.

1. 1On a production prompt click Fork as test and give a suffix (such as test0930 or your name). The test's Marketplace is “name-suffix”. It copies every cell and setting; shared blocks become local text by default, so editing the test does not affect production (tick “The test copy keeps sharing these blocks” to keep sharing, in which case editing a shared block in the test changes production too).
2. 2The fork itself does not touch Airtable. Only the first time you push this test prompt is a row created in the Prompt Manager (along with the Marketplace option, if you have the permission).
3. 3To try it: in the Listing Generator choose “Other…” as the Marketplace and type this test name; listings are then generated with the test prompt.
4. 4When it is good, click Merge back to production on the test prompt: it lists the differences from the production prompt, you tick the changes to move back and click Apply to the production prompt. This only changes the production prompt in the tool; the production row in Airtable has not been touched. To make it take effect, open the production prompt, “Push to Airtable”, and Publish if needed.

New

New at the top left: ① where to start from: any existing prompt, or blank; ② classification: Marketplace (or a new Marketplace), Env (production / test; a test needs a suffix), 1 / 2 calls, Scope, Prompt Name. When copying from another marketplace's prompt you can tick to replace the marketplace name in the text too.

Until its first push a new prompt exists only in Supabase (a draft); the first push creates the row in Airtable. A new Marketplace is used as a custom name for now (like “Other…” in the Listing Generator); to become an official marketplace a developer also has to add it to supabase/functions/_shared/marketplaces.ts.

Delete: retire first, then confirm twice

1. 1Retire first: if the prompt has a live version in Supabase, its Scope is changed to REMOVE — retire this prompt (no new version), only the Scope and Publish fields in Airtable are written, and sync-prompts recognises it and turns the live version into RETIRED (the history is kept). A production marketplace asks you to type the marketplace name to confirm. With no live version this step is not needed.
2. 2The first confirmation: read the list and tick it. Deleted: this row in Airtable, the prompt's source in Supabase. Not deleted: versions already published (RETIRED, kept as a record); the shared blocks it uses; the test copies forked from it (they only lose “forked from”). It tells you which Scopes will have no prompt after the deletion. All categories is the catch-all; without it, products that no more specific prompt matches will fail to generate.
3. 3The second confirmation: type this prompt's name and click Delete permanently.

If someone deleted the row in Airtable, the list marks it “No longer in Airtable”: pushing again creates a new row (with a new Prompt Code), or click Not needed — delete this prompt….