---
title: Automations guides and connectors - Polaris Prompts
description: Prompt engineering guidance and example prompts for Contentstack Polaris Chat in Agent OS.
url: /agent-os/polaris-prompts
product: Contentstack
doc_type: guide
audience:
  - developers
  - content-operations
  - administrators
version: Early Access
last_updated: 2026-04-08
---

# Automations guides and connectors - Polaris Prompts

This page explains how to write effective prompts for Contentstack Polaris (Agent OS) and provides example prompts for common content operations workflows. It is intended for users working with Polaris Chat inside Contentstack who want better outcomes for content management, automation, and reporting.

Polaris Prompts

**Note:** **Agent OS** is currently in **Early Access**. Features may change and limitations may apply. We recommend using it in non-production environments until general availability. For more information, contact [support](mailto:support@contentstack.com).

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.

## Tips for Effective Polaris Prompts
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.

## Example Prompts for Content Operations
Below are customized examples for common workflows you can perform using the Polaris Chat inside Contentstack:

### Entry operations
**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.*

### Asset operations
**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.*

### Visual Editor operations
**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.*

### User guidance
**Explanation:** These questions extract instructional help and architectural guidance.

**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?*

### Visualization
**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.*

## Common questions

### What is prompt engineering in the context of Contentstack Polaris?
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.

### When should I break a prompt into smaller pieces?
Break complex tasks into smaller pieces when you want to boost prompt quality and get more precise results.

### What kinds of workflows can Polaris prompts support?
They can support entry operations, asset operations, Visual Editor operations, user guidance, and visualization for reporting and decision support.

### Should I use Agent OS in production?
**Agent OS** is currently in **Early Access**. Features may change and limitations may apply, and it is recommended to use it in non-production environments until general availability.