contentful

Comprehensive Contentful REST API guide. Covers Content Management API (CMA) for creating/updating content, Content Delivery API (CDA) for fetching published content, Preview API, Images API, and GraphQL API. All examples use curl/HTTP — language-agnostic.

Explain core Contentful concepts and route users to the right implementation skill or documentation. Use when users ask conceptual questions, need terminology clarified, want help choosing between APIs (CDA/CMA/CPA/GraphQL), or need guidance on the Contentful MCP server. Also triggers on "Contentful 101", "which Contentful API", "how do I get started", "which skill should I use", "what does X mean in Contentful", "Contentful glossary", "CDA vs CPA", "CDA vs GraphQL", "how does Contentful work", "Contentful architecture", "explain environments", "what are aliases", "content model design", "headless CMS", "Contentful MCP", "MCP server", "set up MCP", "Remix Contentful", "Astro Contentful", "Gatsby Contentful", "SvelteKit Contentful", "Nuxt Contentful". Not for framework-specific implementation (contentful-nextjs), migrations (contentful-migration), personalization (contentful-personalization), or hands-on REST/GraphQL request examples (contentful-api).

Write and run Contentful content model migration scripts using the contentful-migration library and the Contentful CLI. Covers creating, editing, and deleting content types and fields, validations, editor interface configuration, editor layouts, sidebar widgets, entry transformations, tags, annotations, and the migration context object. Use when asked to write a migration, create or add a content type, add, rename, or delete fields, change or update a content model, transform entries, derive linked entries, configure editor controls, or run a migration script. Also triggers on "migration script", "contentful-migration", "schema migration", "content model migration", "field validation", "editor interface", "editor layout", "sidebar widget", "moveField", "changeFieldId", "rich text field", "reference field", "link field". Not for SDK client setup or Next.js integration (contentful-nextjs). Not for Contentful terminology or API routing (contentful-guide).

Add and configure Contentful in an existing Next.js project. Covers installing the JavaScript SDK, configuring environment variables, creating production and preview-aware clients, fetching content in App Router or Pages Router, and wiring Draft Mode preview flows. Use when users ask to integrate Contentful with Next.js, fetch entries, set up preview or draft content, or configure the Contentful client. Also triggers on "Contentful SDK Next.js", "contentful.js", "fetch Contentful entries", "get content from Contentful", "Contentful preview", "preview mode", "Contentful environment variables", "Contentful client setup", "create Contentful client", "Pages Router Contentful", "getStaticProps Contentful", "Server Components Contentful", "revalidate Contentful", "ISR Contentful". Not for personalization or Experiences SDK setup (contentful-personalization). Not for non-Next.js frameworks (contentful-guide can route to platform docs).

Implement, extend, and debug Contentful personalization. Use onboarding for new, project-wide, or unknown setups; use extend-existing only for scoped work on an explicitly working integration. Trigger keywords: personalization, optimization, ninetailed, A/B test, experiment, multivariate test, targeting, audience targeting, segments, variants, content variants, set up personalization, implement personalization, enable personalization, personalization not working, personalization broken, personalize this component, am I ready for personalization, experience API, Contentful Experiences, Experiences SDK, Studio Experiences, personalization in Next.js, @contentful/optimization, @ninetailed/experience.js, run an experiment, check this URL, debug this live page, inspect network requests, check console errors, experience.ninetailed.co

Synchronize the Contentful Optimization SDK's public API, behavior, and implementation guidance into concise, runtime-specific references for the contentful-personalization skill. Use when the optimization repository or SDK documentation changes, when modern SDK guidance appears stale, or when validating that the skill matches an immutable upstream revision.

Design, scaffold, build, and validate a new Contentful App Framework custom app for a customer's own repository or workspace. Use when users want to create a custom app from an idea, choose App Framework locations, build a sidebar app, field editor app, page app, dialog, configuration screen, App Action, or Function-backed app, scaffold with create-contentful-app, or make a locally testable app for an organization-specific Contentful workflow. Also triggers on "build a Contentful app", "custom app from scratch", "App Framework app", "sidebar app", "field editor app", "page app", "app action", and "app function". Not for generic Contentful API examples (contentful-api), content model migrations (contentful-migration), or website integration (contentful-nextjs).

Improve, debug, and extend an existing Contentful App Framework custom app in a customer's own repository. Use when users provide a bug report, feature request, support note, customer feedback, or direct change request for an existing custom app, including app configuration, sidebar, field editor, dialog, page, home, App Action, Function, installation parameters, local validation, or PR preparation. Also triggers on "fix my Contentful app", "improve a custom app", "enhance App Framework app", "debug custom app", "update sidebar app", and "custom app feature request". Not for creating a brand new app from scratch (contentful-custom-app-from-scratch), generic API examples (contentful-api), migrations (contentful-migration), or website integration (contentful-nextjs).

Diagnose, configure, and look up Contentful topics. Trigger keywords: contentful help, contentful doctor, contentful setup

A guided game creation skill that walks you through designing, planning, and building a browser-based Tetris game. Demonstrates all SDK primitives: askUser, confirm, plan, checklist, and subagent. Trigger keywords: game jam, build a game, tetris, game tutorial

A playful interview that gets to know the user and produces a profile trading card. Use when the user wants to introduce themselves or when you want to break the ice. Trigger keywords: introduce myself, trading card, get to know me, ice breaker

Exercises every SDK primitive in a single skill. Used as a reference and integration test.

TypeScript patterns and idioms reference. Use when writing TypeScript and need a quick refresher on generics, discriminated unions, builder patterns, or error handling.

Author or revise a public documentation guide under documentation/guides/ for the Optimization SDK Suite. Covers the guide archetypes (integration, decision, supplemental recipe), the teach-first quick-start-then-deepen structure, the copy-vs-adapt example labels, the guides directory routing index, and the self-review checklist that keeps guides consistent. Use when writing a new integration guide, rewriting an existing one, adding a decision or recipe guide, editing the guides README index, reviewing a guide for structure and voice, or editing any file under documentation/guides/. Triggers on "write a guide", "integration guide", "getting started guide", "documentation/guides", "choosing-the-right-sdk", "guide archetype", "quick start", "rewrite the guide", "guide TOC", "Copy this / Adapt this". Not for concept docs under documentation/concepts (those own deeper mechanics), not for package or implementation READMEs, and not for generated TypeDoc under docs/.

Maintain the internal SDK knowledge base under documentation/internal/sdk-knowledge/ — the layer of verified SDK behavioral facts (defaults, fallbacks, ownership, lifecycle, cross-runtime semantics) that each carry a source pointer into packages/**/src. Covers the three-artifact split (guides teach, this KB records verified facts, the authoring skill holds principles — facts never go in a skill), the _template.md skeleton every per-SDK file copies, and capturing shared facts once in shared/ so guide families reuse one canonical wording. Use when adding or editing a per-SDK knowledge file, recording an SDK API you just verified against source while doing other work, reading the KB before re-grepping the SDK, keeping it in sync after the SDK changes, or editing any file under documentation/internal/sdk-knowledge/. Triggers on "sdk knowledge", "internal knowledge base", "record verified facts", "source pointer". Not guide prose and not the authoring skill.

Verify a documentation guide's load-bearing SDK claims — the technical-foundation review role — splitting each into interface vs. behavior. Interface claims (symbol existence, signature, prop names/types, optionality, unions, return shape, import path) are checked directly against the types in packages/**/src — a cheap, self-verifying lookup. Behavioral claims (fallback contracts, dynamic-render forcing, batching, defaults, identifier ownership, cross-SDK semantics) are checked against verified facts in documentation/internal/sdk-knowledge/ and must NOT be re-traced from source; a behavioral claim with no backing fact is escalated to sdk-knowledge-authoring. Use as the third authoring role (writer → newcomer reviewer → technical-foundation reviewer), after a guide is drafted or refreshed, or to fact-check a specific claim. Triggers on "technical review", "verify against source", "fact-check the guide", "is this API real", "foundation review". Not reader-experience review (guide-newcomer-review) and not prose

Derive verified SDK facts from source into the internal knowledge base under documentation/internal/sdk-knowledge/ — the comprehension step of the docs pipeline. This is the one expensive step that reads packages/**/src; the knowledge base memoizes it so guides and reviews read facts instead of re-comprehending code. Two modes: BOOTSTRAP (read an SDK's whole public surface into a new KB file, once) and INCREMENTAL (a source change → re-verify only the facts whose pointers hit the changed files, plus capture new/removed exports in that area). Use when a source PR touches packages/**/src, when a new SDK needs a KB file, or when a guide/review escalates a missing fact. Triggers on "update the knowledge base from source", "source changed", "bootstrap KB", "which facts changed", "capture new exports". Not guide prose (optimization-guide-authoring), not the format rules (sdk-knowledge-maintenance), not reader review (guide-newcomer-review).

Review a documentation guide under documentation/guides/ as an average developer with little or no personalization background — the guide's actual target reader. Catches undefined jargon, skim-mode triggers, unperformable verify steps, and forward references that assume knowledge the reader does not have yet. Reports reader-experience findings; it does not verify SDK facts against source (that is guide-source-verification) and does not restructure prose (that is optimization-guide-authoring). Use when reviewing a new or rewritten guide before it ships, as the second of the three authoring roles (writer → newcomer reviewer → technical-foundation reviewer). Triggers on "newcomer review", "review this guide", "read it cold", "average developer review", "docs reviewer".