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.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, integrations, and target platforms.
Identify:
- Type: Native integrations, plugins, extensions, API, webhooks
- Platforms: Which to feature (Slack, Notion, Figma, etc.)
- Format: Single page vs. per-integration pages
- Primary goal: Install, connect, sign up
Page Structure
| Section |
Purpose |
| Headline |
"Integrate with [Platforms]" or "Connect [Product] to Your Stack" |
| Value |
Why integrations matter; workflow benefits |
| Catalog |
Grid or list: logo, name, short description, "Connect" or "Install" |
| Categories |
By use case (Productivity, Design, Dev) or platform type |
| API |
Link to api-page or docs if developer-focused |
| CTA |
Browse all, request integration, build your own |
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
Content
- Per integration: Logo, 1–2 sentence benefit, "Connect" CTA
- Use cases: "Use with Slack to get notifications"
- Screenshots: Show connected workflow when possible
SEO
- Intent: Informational + commercial; "X integration," "X plugin"
- Title: "Integrations | Connect [Product] to [Platforms]" or "[Product] + Slack"
- Internal links: API, docs, features, pricing
Output Format
- Headline and value proposition
- Catalog structure (categories, layout)
- Per-integration copy (name, benefit, CTA)
- Internal links (API, docs)
- SEO metadata
Related Skills
- card: Integration card structure; logo, name, description, CTA; catalog grid
- grid, list: Catalog layout; grid or list format
- 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
1---2name: integrations-page-generator3description: When the user wants to create, optimize, or audit integrations, plugins, or extensions pages. Also use when the user mentions "integrations page", "plugins", "extensions" or "add-ons". For sitewide page planning, use website-structure.4metadata:5 source: https://skillmd.com/skills/ariadoss/integrations-page-generator6 version: 1.0.17---89# Pages: Integrations / Plugins1011Guides integrations, plugins, and extensions pages. Shows how the product connects with Canva, Slack, Zapier, and other platforms. Common for SaaS, tools, and developer products.1213**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.1415## Initial Assessment1617**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, integrations, and target platforms.1819Identify:201. **Type**: Native integrations, plugins, extensions, API, webhooks212. **Platforms**: Which to feature (Slack, Notion, Figma, etc.)223. **Format**: Single page vs. per-integration pages234. **Primary goal**: Install, connect, sign up2425## Page Structure2627| Section | Purpose |28|---------|---------|29| **Headline** | "Integrate with [Platforms]" or "Connect [Product] to Your Stack" |30| **Value** | Why integrations matter; workflow benefits |31| **Catalog** | Grid or list: logo, name, short description, "Connect" or "Install" |32| **Categories** | By use case (Productivity, Design, Dev) or platform type |33| **API** | Link to api-page or docs if developer-focused |34| **CTA** | Browse all, request integration, build your own |3536## Best Practices3738### Organization3940- **By category**: Productivity, Design, Marketing, Dev tools41- **By platform**: Slack, Notion, Figma, Zapier42- **Search/filter**: For 20+ integrations43- **Featured**: Highlight top 5–10; rest in catalog4445### Content4647- **Per integration**: Logo, 1–2 sentence benefit, "Connect" CTA48- **Use cases**: "Use with Slack to get notifications"49- **Screenshots**: Show connected workflow when possible5051### SEO5253- **Intent**: Informational + commercial; "X integration," "X plugin"54- **Title**: "Integrations | Connect [Product] to [Platforms]" or "[Product] + Slack"55- **Internal links**: API, docs, features, pricing5657## Output Format5859- **Headline** and value proposition60- **Catalog structure** (categories, layout)61- **Per-integration** copy (name, benefit, CTA)62- **Internal links** (API, docs)63- **SEO** metadata6465## Related Skills6667- **card**: Integration card structure; logo, name, description, CTA; catalog grid68- **grid, list**: Catalog layout; grid or list format69- **api-page-generator**: API overview; link for developer integrations70- **docs-page-generator**: Integration setup guides in docs71- **category-page-generator**: Catalog layout for many integrations72- **landing-page-generator**: Integration-specific landing pages