contentful-guide

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Contentful Guide

Contentful 指南

Use this skill as the routing and vocabulary layer for Contentful tasks.
Contentful is a headless, API-first CMS (composable content platform) where teams model content once and deliver it to many channels.
将本技能用作Contentful任务的路由与术语解释层。
Contentful是一款无头、API优先的CMS(可组合内容平台),团队只需一次建模内容,即可将其分发至多个渠道。

What this skill does

本技能的功能

  1. Clarifies core terms (space, environment, environment alias, content model, content type, entry, asset, locale).
  2. Maps user intent to the right API (CDA, CPA, CMA, GraphQL, Images API).
  3. Routes implementation requests to the right skill and docs.
  4. Prevents incorrect setup by identifying when a request is not in this skill's scope.
  1. 澄清核心术语(space、environment、environment alias、content model、content type、entry、asset、locale)。
  2. 根据用户意图匹配合适的API(CDA、CPA、CMA、GraphQL、Images API)。
  3. 将实现请求引导至对应的技能与文档。
  4. 通过识别请求是否超出本技能范围,避免错误设置。

Routing rules

路由规则

  • If the user asks to add Contentful to a Next.js project, use the contentful-nextjs skill.
  • If the user asks about optimization/personalization/analytics setup or debugging, route to the
    contentful-personalization
    skill.
  • If the user asks to write content type migrations or schema changes, route to the
    contentful-migration
    skill.
  • If the user asks for concrete REST/GraphQL requests (curl examples, headers, query parameters, payload shapes for CMA/CDA/CPA/Images/GraphQL), route to the
    contentful-api
    skill.
  • If the user asks for conceptual guidance, architecture tradeoffs, or where to read docs, stay in this skill.
  • If the user asks about environment aliases and deployment workflows, stay in this skill unless they also ask for framework implementation.
  • 如果用户询问如何将Contentful添加到Next.js项目中,请使用contentful-nextjs技能。
  • 如果用户询问优化/个性化/分析的设置或调试问题,请引导至
    contentful-personalization
    技能。
  • 如果用户询问编写内容类型迁移或架构变更的问题,请引导至
    contentful-migration
    技能。
  • 如果用户询问具体的REST/GraphQL请求(如curl示例、请求头、查询参数、CMA/CDA/CPA/Images/GraphQL的负载格式),请引导至
    contentful-api
    技能。
  • 如果用户询问概念性指导、架构权衡或文档查阅路径,请使用本技能作答。
  • 如果用户询问环境别名与部署工作流的问题,请使用本技能作答,除非同时涉及框架实现需求。

API chooser

API选择指南

  • Use CDA for published delivery content in websites/apps.
  • Use CPA for unpublished preview content.
  • Use CMA for write operations (create/update/manage content and models).
  • Use GraphQL Content API when query shape control is preferred over REST payloads.
  • Use Images API for image transformations.
  • 使用CDA获取网站/应用中已发布的交付内容。
  • 使用CPA获取未发布的预览内容。
  • 使用CMA执行写入操作(创建/更新/管理内容与模型)。
  • 当需要控制查询结构而非使用REST负载时,使用GraphQL Content API
  • 使用Images API进行图片转换。

Contentful MCP note

Contentful MCP 说明

  • The Contentful MCP server is often the easiest way to let an agent interact with Contentful.
  • Use it when the user wants conversational access to spaces, entries, and content model context without wiring SDK code first.
  • Canonical docs:
    https://www.contentful.com/developers/docs/tools/mcp-server/
  • Contentful MCP服务器通常是让Agent与Contentful交互的最简单方式。
  • 当用户希望无需先编写SDK代码,即可通过对话方式访问spaces、entries和内容模型上下文时,可使用该服务器。
  • 官方文档:
    https://www.contentful.com/developers/docs/tools/mcp-server/

Operating pattern

操作模式

When answering with this skill:
  1. Define terms using shared vocabulary from
    references/lexicon.md
    .
  2. Pick the right docs path from
    references/docs-map.md
    .
  3. If implementation is requested, hand off using
    references/skill-routing.md
    .
  4. Keep answers concise and cite canonical docs paths.
使用本技能作答时:
  1. 参考
    references/lexicon.md
    中的共享词汇表定义术语。
  2. references/docs-map.md
    中选择合适的文档路径。
  3. 如果用户请求实现指导,请通过
    references/skill-routing.md
    转接至对应技能。
  4. 保持回答简洁,并引用官方文档路径。

Guardrails

约束规则

  • Do not invent product capabilities, API behavior, or limits.
  • Do not provide framework code unless routing to the specialized implementation skill.
  • Prefer official docs over memory when details may be version-sensitive.
  • 不得虚构产品功能、API行为或限制。
  • 除非转接至专门的实现技能,否则不得提供框架代码。
  • 当细节可能随版本变化时,优先参考官方文档而非依赖记忆。

References

参考资料

  • Lexicon
  • Docs map
  • Skill routing
  • 术语表
  • 文档映射
  • 技能路由