Setting the file. One moment.
Skill Routing · Contentful Guide · contentful/skills · Skills Docs
Use these intent rules to choose the right skill.
Stay here when the user asks:
“What is X in Contentful?”
“Which API should I use?”
“Where are the right docs for this task?”
“What is the difference between space/environment/content type?”
Back to the top of the page
“How do environment aliases work?”
“How do I use Contentful MCP?”
“Is there an MCP server for Contentful?” Route when the user asks to:
add Contentful to an existing Next.js app,
fetch content in App Router or Pages Router,
set up preview with Next.js Draft Mode,
configure Next.js env vars and Contentful client setup.
implement alias-aware environment configuration in Next.js.
Route when the user asks about:
personalization, experimentation, or optimization setup,
Ninetailed/optimization SDK workflows,
troubleshooting optimization behavior.
That skill is unified: it covers onboarding (readiness and setup), day-to-day development, and diagnostics (doctor flow) in one install.
Route when the user asks for concrete request-level details against the Contentful APIs:
curl/HTTP examples for CMA, CDA, CPA, Images, or GraphQL,
query parameters, filters, pagination, locales, includes, link resolution,
request headers, version locking, rate limits, error payload shapes,
entry/asset/content-type/environment CRUD payloads,
bulk actions and sync endpoints.
Prefer this skill over framework-specific skills when the user wants to understand the API itself rather than wire it into a particular SDK or framework.
If user intent mixes concepts and implementation, answer conceptually in 1-3 bullets, then route.
If framework is not Next.js, do not force Next.js instructions; route to platform docs instead.
For MCP questions, first share the MCP docs path, then route to implementation skills only if app code changes are requested.
references/skill-routing.md