integrations-page-generator

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Pages: Integrations / Plugins

页面:集成 / 插件

Guides integrations, plugins, and extensions pages. Shows how the product connects with Canva, Slack, Zapier, and other platforms. Common for SaaS, tools, and developer products.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
用于指导集成、插件和扩展页面的设计制作,展示产品如何与Canva、Slack、Zapier及其他平台连接,常用于SaaS、工具类及开发者产品。
调用规则:首次使用时,如果合适,可以先用1-2句话介绍本技能覆盖的范围及价值,再提供主要输出。后续调用或用户要求跳过介绍时,直接输出主要内容即可。

Initial Assessment

初始评估

Check for product marketing context first: If
.claude/product-marketing-context.md
or
.cursor/product-marketing-context.md
exists, read it for product, integrations, and target platforms.
Identify:
  1. Type: Native integrations, plugins, extensions, API, webhooks
  2. Platforms: Which to feature (Slack, Notion, Figma, etc.)
  3. Format: Single page vs. per-integration pages
  4. Primary goal: Install, connect, sign up
优先检查产品营销上下文:如果存在
.claude/product-marketing-context.md
.cursor/product-marketing-context.md
文件,读取其中的产品、集成及目标平台相关信息。
确认以下信息:
  1. 类型:原生集成、插件、扩展、API、webhooks
  2. 平台:需要展示的平台(Slack、Notion、Figma等)
  3. 格式:单页面展示 vs 每个集成单独页面
  4. 核心目标:安装、连接、注册

Page Structure

页面结构

SectionPurpose
Headline"Integrate with [Platforms]" or "Connect [Product] to Your Stack"
ValueWhy integrations matter; workflow benefits
CatalogGrid or list: logo, name, short description, "Connect" or "Install"
CategoriesBy use case (Productivity, Design, Dev) or platform type
APILink to api-page or docs if developer-focused
CTABrowse all, request integration, build your own
板块用途
标题"与[平台]集成" 或 "将[产品]连接到你的技术栈"
价值说明集成的重要性;工作流相关收益
目录网格或列表形式:logo、名称、简短描述、"连接"或"安装"按钮
分类按使用场景(生产力、设计、开发)或平台类型划分
API面向开发者的产品可添加API页面或文档的链接
CTA浏览全部、请求集成、自行构建

Best Practices

最佳实践

Organization

组织逻辑

  • By category: Productivity, Design, Marketing, Dev tools
  • By platform: Slack, Notion, Figma, Zapier
  • Search/filter: For 20+ integrations
  • Featured: Highlight top 5–10; rest in catalog
  • 按类别:生产力、设计、营销、开发工具
  • 按平台:Slack、Notion、Figma、Zapier
  • 搜索/筛选:集成数量超过20个时提供
  • 精选:优先展示Top 5-10个集成,其余放在目录中

Content

内容要求

  • Per integration: Logo, 1–2 sentence benefit, "Connect" CTA
  • Use cases: "Use with Slack to get notifications"
  • Screenshots: Show connected workflow when possible
  • 单个集成:Logo、1-2句话的价值说明、"连接"CTA
  • 使用场景:"搭配Slack使用可接收通知"
  • 截图:尽可能展示连接后的工作流效果

SEO

SEO优化

  • Intent: Informational + commercial; "X integration," "X plugin"
  • Title: "Integrations | Connect [Product] to [Platforms]" or "[Product] + Slack"
  • Internal links: API, docs, features, pricing
  • 用户意图:信息类+商业类;"X集成"、"X插件"
  • 页面标题:"集成 | 将[产品]连接到[平台]" 或 "[产品] + Slack"
  • 内部链接:API、文档、功能、定价页

Output Format

输出格式

  • Headline and value proposition
  • Catalog structure (categories, layout)
  • Per-integration copy (name, benefit, CTA)
  • Internal links (API, docs)
  • SEO metadata
  • 标题和价值主张
  • 目录结构(分类、布局)
  • 单个集成文案(名称、价值、CTA)
  • 内部链接(API、文档)
  • SEO元数据

Related Skills

相关技能

  • api-page-generator: API overview; link for developer integrations
  • docs-page-generator: Integration setup guides in docs
  • category-page-generator: Catalog layout for many integrations
  • landing-page-generator: Integration-specific landing pages
  • api-page-generator:API概览;开发者集成相关链接
  • docs-page-generator:文档中的集成配置指南
  • category-page-generator:多集成的目录布局
  • landing-page-generator:特定集成的落地页