datocms-setup

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

DatoCMS Setup

DatoCMS 设置

This is the single public setup entrypoint for DatoCMS project scaffolding. Keep the public surface small, inspect the repo first, and load only the internal recipe files needed for the user's requested outcome.

这是DatoCMS项目脚手架的唯一公开设置入口。保持公开接口简洁，先检查仓库，仅加载用户所需成果对应的内部预设方案文件。

Workflow

工作流

Silently inspect the repo before asking questions, following
```
references/repo-conventions.md
```
and the shared rules in
```
patterns/MANDATORY_RULES.md
```
.
Read
```
references/router.md
```
.
Read
```
references/recipe-manifest.json
```
and select the smallest recipe or internal bundle that satisfies the request.
Use targeted mode when the request clearly names a setup outcome. Use discovery mode only when the request is broad or ambiguous:
- Stage A picks the setup lane.
- Stage B asks the smallest setup-specific follow-up only when repo inspection still leaves a high-impact decision unresolved.
Queue prerequisites from the manifest before dependent recipes. Never tell the user to invoke another setup skill separately.
- For
```
visual-editing
```
  , always apply
```
draft-mode
```
  and
```
content-link
```
  .
- Add
```
web-previews
```
  unless the user explicitly wants website-only click-to-edit.
- Add
```
realtime
```
  only when the user explicitly asks for live updates or confirms them in the Stage B follow-up.
Load only the selected
```
recipes/<group>/<recipe>/recipe.md
```
files, the shared setup references they call for, and the sibling-skill references they point to.
Patch existing project code in place by default instead of rewriting working implementations.
End with the shared handoff contract in
```
patterns/OUTPUT_STATUS.md
```
: report
```
scaffolded
```
vs
```
production-ready
```
, summarize the selected recipes, and list unresolved placeholders explicitly.

在提问前先静默检查仓库，遵循
```
references/repo-conventions.md
```
和
```
patterns/MANDATORY_RULES.md
```
中的共享规则。
阅读
```
references/router.md
```
。
阅读
```
references/recipe-manifest.json
```
，选择能满足请求的最小预设方案或内部包。
当请求明确指定设置成果时使用目标模式。仅当请求宽泛或模糊时使用发现模式：
- 阶段A选择设置方向。
- 阶段B仅当仓库检查仍无法解决高影响决策时，提出最简短的设置相关后续问题。
在执行依赖预设方案前，先从清单中加载前置条件。切勿告知用户单独调用其他设置技能。
- 对于
```
visual-editing
```
  ，始终先应用
```
draft-mode
```
  和
```
content-link
```
  。
- 除非用户明确要求仅支持网站端点击编辑，否则添加
```
web-previews
```
  。
- 仅当用户明确要求实时更新或在阶段B后续确认时，才添加
```
realtime
```
  。
仅加载所选的
```
recipes/<group>/<recipe>/recipe.md
```
文件、它们所需的共享设置参考文档，以及指向的同级技能参考。
默认情况下，在现有项目代码基础上进行补丁修改，而非重写可运行的实现。
以
```
patterns/OUTPUT_STATUS.md
```
中的共享交付规则结束：报告
```
scaffolded
```
（已搭建）或
```
production-ready
```
（生产就绪）状态，总结所选预设方案，并明确列出未解决的占位符。

Rules

规则

Do not load every recipe up front.
Do not reference or depend on any external setup bundles. Prefer sibling DatoCMS skill references over copied duplicates when a recipe reuses existing documentation.
Treat recipe ids such as
```
draft-mode
```
,
```
web-previews
```
,
```
visual-editing
```
, and
```
migration-release-workflow
```
as internal orchestration labels.
If several requested outcomes share a foundation, apply that foundation once and continue through the queued recipes.
If the user asks for broad setup, ask one compact grouped Stage A clarification pass, then execute the minimal recipe bundle.
Use Stage B only for unresolved, high-impact setup decisions that the repo cannot answer safely.
For migration-heavy requests, ask the smallest extra grouped follow-up needed to separate baseline migrations, named profiles, shared histories, release helpers, sandbox reset loops, and diff-based generation.
Report
```
scaffolded
```
when a recipe still depends on placeholders, provider choices, route mappings, or unresolved ownership the repo could not resolve automatically.
Report
```
production-ready
```
only when the selected recipe no longer depends on unresolved customer-specific values.
End by summarizing which internal recipes were used and which optional follow-up recipe ids are available inside
```
datocms-setup
```
.

不要预先加载所有预设方案。
不要引用或依赖任何外部设置包。当预设方案复用现有文档时，优先引用同级DatoCMS技能，而非复制副本。

将

draft-mode

、

web-previews

、

visual-editing

和

migration-release-workflow

等预设方案ID视为内部编排标签。

如果多个请求的成果共享同一基础，仅应用一次该基础，然后继续执行队列中的预设方案。
如果用户要求宽泛的设置，先进行一次简洁的分组阶段A澄清，然后执行最小的预设方案包。
仅当仓库无法安全解决未决的高影响设置决策时，才使用阶段B。
对于迁移需求较多的请求，提出最简短的分组后续问题，以区分基线迁移、命名配置文件、共享历史、发布助手、沙箱重置循环和基于差异的生成。
当预设方案仍依赖占位符、服务商选择、路由映射或仓库无法自动解决的未决归属问题时，报告
```
scaffolded
```
状态。
仅当选定的预设方案不再依赖未解决的客户特定值时，才报告
```
production-ready
```
状态。
结束时总结使用了哪些内部预设方案，并列出
```
datocms-setup
```
中可用的可选后续预设方案ID。