Back to Details

moda-templates

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

moda-templates

moda-templates

<!-- moda:banner -->
PREREQUISITE — load 
moda-core
once per session (step-0, write contract, free/metered map). Already loaded? Skip ahead. If you cannot load it, the non-negotiables: run 
moda doctor --json
before anything; 
moda brand list
before creating; every write carries the latest revision — on 
stale_revision
, re-read and retry once (it heals); send the canvas link the moment it exists; stuck or failed? 
moda ask "<question>"
— free and fast, never guess.
<!-- /moda:banner -->
A team template is the canvas someone approved as the starting point for recurring work — the QBR deck, the launch post, the customer one-pager. It carries layout and structure, one level up from what a brand kit carries.
<!-- moda:banner -->
前提条件——每个会话仅加载一次
moda-core
（步骤0，编写合约，免费/计量映射）。已加载？直接跳过。如果无法加载，必须执行以下操作：先运行
moda doctor --json
；创建前先运行
moda brand list
；每次写入都要携带最新版本——遇到
stale_revision
时，重新读取并重试一次（即可恢复）；画布链接一创建好就发送；遇到问题或失败？使用
moda ask "<question>"
——免费且快速，切勿自行猜测。
<!-- /moda:banner -->
团队模板是指经他人批准、可作为重复性工作起点的画布——比如QBR演示文稿、发布帖、客户单页文档。它承载着布局和结构，比品牌套件的层级更高。

Check before designing (one cheap read)

设计前检查（一次轻量读取）

The ask names a recurring artifact type (QBR or board deck, launch post, customer one-pager) or the user says "our template", "our usual format", "what do we have" → check first. Skip it for genuine one-offs.
当需求中提到重复性工件类型（如QBR或董事会演示文稿、发布帖、客户单页文档），或用户提到「我们的模板」「我们常用的格式」「我们有哪些模板」时，先进行检查。真正的一次性工作可跳过此步骤。

Instantiate

实例化流程

  1. moda template list
    — id, name, category, page count. An empty list is a normal answer: say it in one line and design fresh.
  2. LOOK before choosing. Names do not tell you what a template looks like, and a template IS a canvas: 
    moda canvas screenshot [cvs_…]
    renders it inline (≤3 pages per call). Judge 2–4 plausible candidates with your own vision; category and page count do the cheap narrowing first.
  3. Comparing many at once? 
    moda template pull --output /tmp/templates.json
    is the one read whose 
    thumbnail_url
    values are fetchable (
    moda template list
    scrubs them by design) — download those with your harness's own fetch. They expire: never place one in markup, never persist one, never hand one to the user. A null thumbnail means nothing is rendered yet.
  4. moda canvas create --name "[Q3 QBR — Acme]" --template [cvs_…]
    — a full server-side copy that keeps the source's brand kit. The template defines size, pages, and category, so 
    --size
    , 
    --pages
    , 
    --category
    , 
    --intent
    , 
    --folder
    , 
    --visibility
    and 
    --brand
    are REJECTED alongside it; place the copy afterwards with 
    moda drive move
    , and rebind its kit with 
    moda canvas brand [cvs_…] [bk_…]
    when the user's kit differs.
  5. The copy is an ordinary canvas — read it, then edit it the normal way (moda-edit). Send the link, and name which template you started from: that is a decision the user may want to correct.
  6. None fit? One line ("no team template matched, so I designed this fresh") and build from scratch. Never force a bad-fit template.
Want a copy of an ordinary canvas instead of a template? 
moda canvas duplicate [CANVAS_REF] --name "…"
is the as-is copy of anything you can read.
  1. moda template list
    ——返回模板的ID、名称、分类、页数。空列表是正常结果：用一句话说明后从头设计即可。
  2. 选择前先查看。名称无法体现模板的实际样式，而模板本身就是画布：
    moda canvas screenshot [cvs_…]
    可在线渲染模板（每次调用最多显示3页）。结合你的判断筛选2-4个合适的候选模板；可先通过分类和页数快速缩小范围。
  3. 如需同时对比多个模板？
    moda template pull --output /tmp/templates.json
    是唯一能获取
    thumbnail_url
    的读取操作（
    moda template list
    默认会隐藏该字段）——可通过你的工具自行下载缩略图。注意：缩略图会过期，切勿将其放入标记语言、持久存储或提供给用户。
    null
    缩略图表示尚未生成渲染内容。
  4. moda canvas create --name "[Q3 QBR — Acme]" --template [cvs_…]
    ——在服务器端完整复制模板，保留源模板的品牌套件。模板已定义尺寸、页数和分类，因此
    --size
    、
    --pages
    、
    --category
    、
    --intent
    、
    --folder
    、
    --visibility
    和
    --brand
    参数会被拒绝；如需调整位置，可后续使用
    moda drive move
    ，若用户的品牌套件不同，可使用
    moda canvas brand [cvs_…] [bk_…]
    重新绑定。
  5. 复制得到的是普通画布——读取后即可按常规方式编辑（moda-edit）。发送画布链接，并说明使用的起始模板：用户可能需要纠正这一选择。
  6. 没有合适的模板？用一句话说明（「没有匹配的团队模板，因此我从头设计了这个内容」），然后从零开始构建。切勿强行使用不合适的模板。
如需复制普通画布而非模板？使用
moda canvas duplicate [CANVAS_REF] --name "…"
可原样复制任何你有权读取的内容。

Flag a canvas as the team's template

将画布标记为团队模板

moda canvas template [cvs_…]                 # publishes it to the whole team
moda canvas template [cvs_…] --clear         # un-flag
  • Team-visible curation, not a local preference. Offer it when the user calls something reusable ("we do this every quarter"); never flag a one-off, never flag unasked, and tell them once you have.
  • Original should stay an ordinary canvas? 
    moda canvas duplicate
    first, then flag the copy. Flag in place when the canvas was BUILT to be the template.
  • moda template list
    hides canvases the viewer cannot see, so flagging a private canvas yields a template only you can find: 
    moda drive visibility [cvs_…] team
    shares it — or say plainly you could not.
moda canvas template [cvs_…]                 # 向整个团队发布该模板
moda canvas template [cvs_…] --clear         # 取消标记
  • 这是团队可见的整理操作，而非本地偏好。当用户提到某内容可复用（「我们每季度都做这个」）时，可提供此功能；切勿标记一次性内容，切勿未经请求就标记，标记后需告知用户。
  • 若希望原画布保持普通画布状态？先使用
    moda canvas duplicate
    复制，再标记副本。如果画布本身就是为模板打造的，可直接标记原画布。
  • moda template list
    会隐藏查看者无权访问的画布，因此标记私有画布后，只有你能找到该模板：可使用
    moda drive visibility [cvs_…] team
    共享画布——或直接说明无法共享。

theme
is a different thing — don't reach for it

theme
是不同的功能——请勿混淆

moda canvas template [cvs_…] theme
is a slides-only layout source applied through a brand kit, and it deliberately does NOT appear in 
moda template list
. Moving a canvas OFF 
theme
— to 
template
or with 
--clear
, both count — clears every deck's link to it and every kit that auto-applied it, and re-flagging restores none of them. On a canvas you did not flag yourself, read 
moda canvas show [cvs_…]
(
template_type
) BEFORE writing.
moda canvas template [cvs_…] theme
是仅适用于幻灯片的布局源，通过品牌套件应用，且不会出现在
moda template list
中。将画布从
theme
切换为
template
或使用
--clear
取消绑定，会清除所有演示文稿与它的关联，以及所有自动应用它的品牌套件，重新标记也无法恢复这些关联。对于非你标记的画布，写入前请先查看
moda canvas show [cvs_…]
的
template_type
字段。

Examples

示例

  • "start from our QBR template" → list, screenshot the QBR candidates, create with 
    --template
    , then author into the copy.
  • "use our usual layout for this one-pager" → same flow, filtered to 1–2 page document templates.
  • "make this our standard deck" → flag it (after checking 
    template_type
    ).
  • "do we have anything for launches?" → list + screenshots, answer honestly if the answer is no.
  • 「从我们的QBR模板开始」→ 列出模板、截图QBR候选模板、使用
    --template
    创建副本，然后编辑副本内容。
  • 「使用我们常用的布局制作这个单页文档」→ 流程相同，筛选1-2页的文档模板。
  • 「把这个设为我们的标准演示文稿」→ 标记它（先检查
    template_type
    ）。
  • 「我们有适用于发布的模板吗？」→ 列出模板并截图，如实告知是否存在匹配模板。

Errors

错误处理

Any typed error → load moda-core and read its recovery reference. A 404 here means the surface is not enabled on this account: treat it exactly like "no templates" — do not retry it, and do not mention it. A 403 means template management is admin-only: say an admin has to flag this one, in one line.
任何输入错误→加载moda-core并查看其恢复参考文档。404错误表示该功能未在当前账户启用：完全按照「无模板」情况处理——不要重试，也不要提及该错误。403错误表示模板管理仅限管理员操作：用一句话说明需要管理员来标记该模板。

Make it recurring

实现自动化重复操作

Every instantiation is a return visit — that is the point. Pair it with moda-automate when the cadence is fixed (a monthly menu, a weekly post set).
See also: moda-core — the contract, recovery, everything Moda can do.
每次实例化都是重复任务的回归——这正是模板的意义所在。当任务有固定周期（如每月菜单、每周发布帖）时，可搭配moda-automate使用。
另请参阅：moda-core——包含合约、恢复方案以及Moda的所有功能。