contentstack

Migration companion for moving to Contentstack from another CMS. Guides content and application migration through a structured, step-by-step workflow. Currently supports migrations from Contentful, with additional source platforms planned. Use when users want to migrate, move, switch, port, or re-platform to Contentstack, including content models, content, assets, locales, application integrations, or website code. Trigger on requests such as "migrate to Contentstack", "move to Contentstack", "switch to Contentstack", "migrate from Contentful", "move my Contentful space", "port my CMS", or similar migration-related requests. The skill validates prerequisites, guides the migration process, provides progress checkpoints, and delivers a completion summary. Prefer this skill whenever a Contentstack migration is requested.

Advise users on Contentstack Brand Kit concepts, setup, governance, and on-brand AI generation. Route API-specific tasks to the right Brand Kit capability or reference skill, and enforce brand and safety rules before presenting anything as ready.

Turn Contentstack Developer Hub and Marketplace app ideas into concrete implementations. Choose the right UI location, map the architecture, generate boilerplate-aligned React/TypeScript code, and troubleshoot setup, SDK, manifest, proxy, and publishing issues.

Help agents write correct, production-ready TypeScript using `@contentstack/delivery-sdk` for Contentstack entries, assets, references, filtering, sorting, pagination, locale, Live Preview, and Visual Builder support. Verify SDK behavior against the Delivery SDK Spec when method names, options, or chain order matter.

Migrate Contentstack Delivery SDK code from JavaScript to TypeScript. Rewrite setup, initialization, Stack, Entries, Assets, Query, pagination, cache, utils, taxonomy, and image transform usage while preserving behavior and calling out TypeScript-specific differences.

Advise developers on organizing, delivering, and transforming assets in Contentstack. Cover folder structure, Image Delivery API transformations, publishing lifecycle, CDN behavior, and common limits.

Advise developers on using Contentstack branches for isolated content development and aliases for zero-downtime content deployments. Cover branch strategy, branch-specific vs global modules, CI/CD integration, merge behavior, and rollback patterns.

Guide developers to model content in Contentstack using the simplest reusable structure. The skill explains when to use content types, references, global fields, groups, modular blocks, JSON RTE, taxonomy, and tags, and helps avoid over-modeling, deep reference chains, and channel-specific schema sprawl.

PR and release checklist for cli-cm-regex-validate (security, packaging, CI, messages)

Contentstack CLI plugin patterns for cm:stacks:validate-regex (SDK, schema, safe-regex, output)

Local and CI workflow for cli-cm-regex-validate — commands, layout, naming, hooks, and merge expectations

Jest testing patterns for cli-cm-regex-validate (mocks, fixtures, no live API calls)

Reviews pull requests and risky changes for the contentstack-cli-content-type plugin. Use when reviewing diffs, security-sensitive edits, dependency upgrades, or changes to compare/diagram/temp-file behavior, ESLint, and tests.

Develops and maintains the contentstack-cli-content-type csdx plugin (content-type list, details, audit, compare, compare-remote, diagram). Use when editing this repository, ContentTypeCommand setup and flags, CMA/Management SDK usage, axios audit/references calls, diff/compare HTML output, Graphviz diagrams, or oclif readme/manifest workflows.

Local build, test, lint, coverage, TypeScript layout, ESLint, and oclif-generated docs for contentstack-cli-content-type. Use when changing package.json scripts, tsconfig, .eslintrc, Jest config, README/oclif manifest, or validating before a PR.

Runs and extends Jest tests for the contentstack-cli-content-type plugin. Use when adding or changing tests under tests/, mocking HTTP or ContentstackClient, configuring Jest, or running npm test and posttest ESLint.

Use when reviewing or preparing a pull request for contentstack-management-dotnet.

Use for branches, CI, build/test scripts, and NuGet release flow in contentstack-management-dotnet.

Use for the contentstack.management.aspnetcore package, HttpClient/DI registration with ASP.NET Core.

Use when changing or using the CMA client API, authentication, or NuGet package surface for Contentstack.Management.Core.

Use for C# language level, nullable usage, and file/folder layout consistent with Contentstack.Management.Core.

Use when building or updating DocFX API documentation under docfx_project for this repository.

Use for target frameworks, assembly signing, NuGet packaging, OS-specific builds, and HTTP pipeline overview in Contentstack.Management.Core.

Use when changing HTTP handlers, retry behavior, or pipeline ordering in Contentstack.Management.Core.Runtime.Pipeline.

Use when reviewing PRs for contentstack-javascript—API compatibility, bundles, Jest, and npm/CDN impact.

Use for the contentstack npm package API—Stack, regions, queries, and @contentstack/utils usage.

Use for npm scripts, Husky, CI, and branch workflow in contentstack-javascript.

Use for Webpack configs, multi-target dist outputs, and Babel/loader setup in contentstack-javascript.

Use for Jest e2e and TypeScript test suites, jest configs, and test layout in contentstack-javascript.

Contentstack Content Delivery (CDA) JavaScript SDK — Stack, tokens, regions, queries, sync, live preview in src/core/.

HTTP and cross-cutting behavior for the CDA SDK — request.js, fetch retries, plugins, runtime http/localstorage.

PR checklist and severity guidance for kickstart-next contributions.

Contentstack Delivery SDK, live preview, getPage, env overrides, and content model alignment for kickstart-next.

Local setup, Contentstack seeding, env vars, CI expectations, and PR ownership for kickstart-next.

Next.js, Tailwind v4, PostCSS, package scripts, and image optimization configuration for kickstart-next.

App Router structure, React components, client vs server, and rendering patterns in kickstart-next.

Test layout and policy for kickstart-next—currently no automated tests; credentials and CI context.

TypeScript compiler options, ESLint setup, and Contentstack entry typing conventions for kickstart-next.

Use when reviewing PRs or preparing changes for contentstack-js-core—API stability, tests, and consumer impact.

Use when working on @contentstack/core API surface, HTTP layer, errors, or how other SDKs consume this package.

Use when changing branches, CI, npm scripts, Husky hooks, or release workflow in contentstack-js-core.

Use when writing or fixing Jest tests, mocks, or test layout under test/ in contentstack-js-core.

Use for TypeScript layout, tsconfig variants, and build outputs (CJS/ESM/UMD/types) in contentstack-js-core.

@contentstack/core — httpClient, request helpers, param serialization, errors, delivery retry handlers.

Axios HTTP stack in @contentstack/core — clients, retries, serialization pipeline.

Use when reviewing PRs for contentstack-marketplace-sdk—API, bundles, tests, and npm publish impact.

Use for npm scripts, CI, and release flow in contentstack-marketplace-sdk.

Use for Babel presets, Webpack configs, and multi-target builds in contentstack-marketplace-sdk.

Use for Marketplace client behavior, public methods in lib/, and axios/@contentstack/utils usage.

Use for Mocha/NYC unit tests, API tests, and Jest TypeScript tests in contentstack-marketplace-sdk.

Mental model for the Marketplace SDK — client factory, org-scoped marketplace API, auth, regions, module map

HTTP stack for marketplace-sdk — Axios wrapper, retries, concurrency, params serialization, logging hook

Use for Android module layout, Gradle config, and Kotlin/Java conventions in contentstack-android.

Use when reviewing PRs for contentstack-android—API stability, Gradle, tests, and mobile security.

Use for the public Android Content Delivery SDK surface and package com.contentstack.sdk.

Use for Gradle tasks, CI, release publishing, and branch flow in contentstack-android.

Use for AGP, Gradle plugins, JaCoCo, signing, and native Android build concerns in contentstack-android.

Use for JVM unit tests, Robolectric, AndroidX Test, and JaCoCo in contentstack-android.

Use when reviewing PRs for the Python CDA SDK — public API, Stack, HTTP layer, tests, secrets.

Use for Stack initialization, queries, entries, assets, live preview, taxonomy, and variants in contentstack-python.

Use for install, pytest, versioning, pre-commit hooks, and PR baseline in contentstack-python.

Use for HTTPSConnection, requests session, urllib3 retries, and timeouts in contentstack-python.

Use for Python package layout, setup.py conventions, and style in contentstack-python.

Use for pytest setup, test layout, config.py credentials, and hygiene in contentstack-python.

Use for Maven lifecycle, CI, JaCoCo, and branch expectations in contentstack-java.

Use when reviewing PRs for contentstack-java—API compatibility, tests, Maven, and security.

Use for the Java Content Delivery API—Stack, Entry, Query, sync, and HTTP/callback patterns.

Use when touching config, retry, or HTTP layer – Config, RetryOptions, RetryInterceptor, CSHttpConnection, connection/request flow, and error handling

Use for Java package layout, language level (8), and project conventions in contentstack-java.

Use for JUnit tests, integration (*IT) tests, fixtures, and credentials handling in contentstack-java.

Branches, CI expectations, Composer test/docs, PR hygiene for Contentstack PHP SDK.

PR checklist—API stability, docs, errors, compatibility, dependencies/SCA, tests; Blocker/Major/Minor.

PHP Delivery SDK API—Contentstack::Stack, queries, entries, assets, regions, sync; RTE via Composer package contentstack/utils.

Composer package, PSR-4 autoload, Doctum docs, PHP version constraints, dev dependencies.

PSR-4 layout, namespaces, docblocks, PHP compatibility, src/ structure for this SDK.

PHPUnit—test/ layout, helpers, constants, coverage output, secrets hygiene.

Use when reviewing PRs for the TypeScript Delivery SDK—API, tests, bundler impact, semver.

Use for the public Delivery SDK API, stack initialization, and integration with @contentstack/core and utils.

Use for branches, CI, npm scripts, and release flow in contentstack-typescript.

Use for Rollup build, browser-safe validation, and bundler compatibility in contentstack-typescript.

Use for Jest, Playwright e2e, API tests, and bundler smoke tests in contentstack-typescript.

Use for TypeScript source layout, Rollup build, and dist outputs in contentstack-typescript.