| Use when users ask about Contentstack Brand Kit, Voice Profiles, Knowledge Vault, brand voice, tone, style rules, on-brand AI generation, setup, governance, or API usage. Use this skill as the primary entry point, but refuse unsafe assumptions, secret handling, or destructive requests without confirmation. | Brand Kit Assistant |
| Use when users want to migrate, move, switch, port, or re-platform from Contentful to Contentstack, including content models, content, assets, locales, application integrations, website code, migration prerequisites, migration progress checks, or post-migration validation. | contentstack-migration-companion |
| Use when a user wants to migrate Contentstack Delivery SDK code from JavaScript to TypeScript. | dx-migrate-js-to-ts-sdk |
| Use when a user asks for Contentstack Delivery SDK code, query examples, helper functions, SDK setup, stack initialization, reference inclusion, filtering, sorting, pagination, typed entry fetching, asset fetching, Live Preview setup, Visual Builder support, SSR preview handling, or debugging SDK query chains. | dx-delivery-sdk |
| Use when designing, reviewing, or refactoring Contentstack content models before creating or changing schemas. | Contentstack Data Modeling Best Practices |
| Use this skill when a user is implementing or debugging Contentstack Live Preview or Visual Builder, including blank preview panels, stale or published-only preview, lost preview context after navigation, shared SSR state, cache contamination, or edit-tag mapping failures. Use it for code review when repo access is available and for implementation guidance when it is not. | Live Preview and Visual Builder Support Assistant |
| Use when developers ask about fetching entries, building CDA queries, handling localization, publishing workflows, versioning behavior, bulk operations, or entry-related performance issues. | Entries |
| Use when developers ask about uploading, organizing, delivering, transforming, publishing, or troubleshooting images and other media files in Contentstack. | Contentstack Assets |
| Use when developers need help classifying content, designing category hierarchies, choosing between taxonomy and other classification approaches, or querying entries by category on the delivery side. | Contentstack Taxonomy |
| Use when developers ask about workflow stage design, approval processes, publish rules, self-approval prevention, transition restrictions, or automation triggered by workflow changes. | Workflows & Publish Rules |
| Use when developers ask about environment setup, publishing behavior, delivery or preview tokens, the Sync API, scheduling, or CDN and caching configuration in Contentstack. | Contentstack Environments & Publishing |
| Use when developers ask about languages, fallback chains, localizing entries, non-localizable fields, or multi-locale publishing. Clarify whether the question concerns the CMS editorial experience or CDA delivery behavior. | Contentstack Localization |
| Use when developers ask about branches, aliases, CI/CD integration with Contentstack, deployment strategies, or branch-specific vs global module behavior. | Branches & Aliases |
| Use when developers ask about user permissions, role design, team management, token capabilities, access control, or automation access in Contentstack. | Roles & Permissions |
| Use when developers ask about deploying multiple content changes together, campaign launches, coordinated content updates, release scheduling, or CI/CD content deployment. | Releases |
| Use when developers ask about authentication, token types, API keys, rate limits, SSO integration, or credential security. | Tokens & Authentication |
| Use when developers need help setting up webhooks, choosing event channels, handling webhook payloads, verifying signatures, debugging delivery issues, or integrating Contentstack with external systems such as site rebuilds, search indexes, Slack, or CI/CD. | Contentstack Webhooks |
Use when a Launch environment must match the keys defined in a local .env.example file. | Sync Launch environment variables from .env.example |
| Use when you need to automate Launch deployments for a known project and environment, monitor progress, and surface failure diagnostics. This is appropriate for CI/CD or operator workflows that need a deterministic deploy status check and log-based troubleshooting. | Trigger and Monitor Launch Deployments |
| Use when developers ask about content personalization, A/B testing, audience segmentation, variant creation, or integrating Personalize with the CMS. | Variants & Personalization |
| Use when a user needs help designing or building a Contentstack Developer Hub or Marketplace app. | Developer Hub App Architect |