Polaris Prompts

Note For access, please talk to our Support team.

Prompt engineering is the practice of writing clear, purposeful instructions for Contentstack Polaris so it can accurately understand your intent and deliver the right outcomes. Well-designed prompts help you get more precise results when managing content, automating workflows, enriching entries, or generating insights across your Contentstack stack.

Here are quick reminders to boost prompt quality:

• Break complex tasks into smaller pieces.
• Mention relevant tools or APIs if needed.
• Ask for explanations, not just output.

Below are customized examples for common workflows you can perform using the Polaris Chat inside Contentstack:

Explanation: These prompts cover creation, improvement, translation, publication, and release planning, key content lifecycle operations in CMS workflows.

Examples:

• Draft a new blog entry about the role of AI in content management.
• Improve the tone and clarity of this blog entry to make it more engaging.
• Translate this blog entry into French, keeping industry terminology accurate.
• Publish this entry to the live environment.
• Tag this entry for the next release cycle and add it to the upcoming release.
• Add a comment on the Body field asking for a link to the content modeling guide, and mention @Jane Doe.
• Read the open comments on this entry, apply the feedback, then resolve the comments you addressed.

Explanation: Good metadata improves search and accessibility; alt text should describe content clearly for both users and search engines.

Examples:

• Update metadata for this image to include SEO-friendly tags.
• Suggest three alternative alt text options for this image based on context.

Explanation: These prompts support marketing operations, from page design to content refinement.

Examples:

• Create a landing page layout for an upcoming product Launch.
• Shorten and sharpen the content on this page to improve readability.
• Which entries does each section of this page come from?
• Add a French version of this page with a suitable French page URL.
• Adapt this page for new visitors: write a more welcoming headline, but only for that audience.
• Give me a link to open the French version of this page.

Explanation: These prompts manage a release from creation to rollback.

Examples:

• Create a release called Spring Launch, add both blog entries to it, and deploy it to the staging environment.
• Roll back the Spring Launch release on staging.

Explanation: These prompts set up stack resources without leaving the conversation.

Examples:

• Create an environment called preview without a base URL.
• Connect the Spring Campaign Personalize project to this stack.
• Create two blog entries and generate their URLs from the content type's URL pattern.

Explanation: These prompts manage access to a stack. Polaris applies the same permissions you have in the UI.

Examples:

• Who has access to this stack? Include pending invitations.
• Invite [email protected] to this stack as a Developer.
• Change [email protected]'s role on this stack to Content Manager.
• Resend the invitation to [email protected].

Explanation: Export prompts turn content into a file you can download.

Examples:

• Export this entry as a Markdown file.
• Export all Blog Post entries as a JSON file.
• Create a PDF of this entry.

Explanation: These questions extract instructional help and architectural guidance. Polaris answers product questions from the Contentstack documentation and links to the relevant guide.

Examples:

• How do I fetch entries in a specific locale using Contentstack APIs?
• Review this content type and recommend improvements for structure and usability.
• What’s the best way to model a blog content type in Contentstack?

Explanation: Visualization prompts help with reporting and decision support.

Examples:

• Show a table of entries broken down by locale.
• Create a chart comparing published vs. unpublished entries.