> For the complete documentation index, see [llms.txt](https://shoppad.gitbook.io/yedric/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shoppad.gitbook.io/yedric/getting-started/prompt.md).

# Prompt

The Instructions tab is where you give Yedric his core instructions. This is the first thing he reads before every conversation, so it shapes everything. The instructions guide him on how he responds, what he focuses on, and how he talks to your users.

<figure><img src="https://3812449461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPjm0d1QYgJndrHFpof4j%2Fuploads%2FARH46mpaTPlInFEIY967%2FST-prompt-page.jpeg?alt=media&amp;token=5d17fe9a-17f7-4e67-a381-ea423787f020" alt="Screenshot of the Prompt tab, focused on the model selector dropdown and the instructions text box."><figcaption><p>Select your model and manage your instructions in the Prompt tab.</p></figcaption></figure>

***

## What to Include

A good system prompt covers a few key things:

* What your app does and who your users are
* What Yedric can and cannot help with
* How you want him to communicate: tone, level of detail, any phrases to avoid
* Any context that helps him give accurate answers specific to your product

The more specific you are, the better Yedric performs. A prompt that says "you are a helpful assistant" will get generic results. A prompt that says "you are a support assistant for a Shopify app that helps customers add custom options to their products" gives Yedric real context to work with.

***

## Autocomplete

While writing your instructions, type `/` to bring up a list of things you can reference directly in the prompt: available tools, skills from your MCP servers (custom integrations your developer may have set up), and any secrets you have stored for this assistant. Selecting one inserts a reference that Yedric can use at runtime.

<figure><img src="https://3812449461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPjm0d1QYgJndrHFpof4j%2Fuploads%2Fvx8j4bIjvOIjGVW6zbFv%2FST-prompt-autocomplete.jpeg?alt=media&amp;token=416d7e21-9af7-4b11-a95e-d9dd096388f2" alt="Screenshot of the instructions editor with the slash (/) autocomplete menu open, focused on the list of tools, skills, and secrets you can insert into the prompt."><figcaption><p>Using "/" will open a menu of options to add to your instructions.</p></figcaption></figure>

***

## Suggestions from the Dashboard

If you have conversations running, the Dashboard analyzes them and may generate a suggested revision to your instructions based on patterns it detects. When a suggestion is ready, recommendations appear in your dashboard. You can apply the suggestion directly to the instructions in your prompt tab or dismiss it if it is not relevant.

<figure><img src="https://3812449461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPjm0d1QYgJndrHFpof4j%2Fuploads%2F3SP2MvVFrkBocu8u1FX3%2FST-prompt-recommendations-dashboard.jpeg?alt=media&amp;token=d364e58e-77f0-44aa-ade0-f72ced8d8cc4" alt="Screenshot of the Dashboard, focused on the recommended actions card suggesting a revision to your instructions."><figcaption><p>Recommended actions appear on your dashboard as conversations are up and running.</p></figcaption></figure>

***

## Updating Your Prompt

You can edit the Name, Model, and System Prompt at any time from this tab. Click **Save Changes** when you are done.

If you want to try a different approach without losing your current setup, use **Duplicate** to create a copy of the assistant first.

***

## Tips

Start with what your support team already knows. If your team answers the same questions every day, the answers to those questions should be in the prompt or the knowledge base.

Use the Conversations tab to see how users are interacting with Yedric. If you notice gaps or misunderstandings, come back here and refine the prompt.