> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/prompt-library-setup.md).

# Prompt library: setup

Prompts to copy into Claude, Cursor or another assistant connected to Jimo, one per setup task, from reading your project to publishing to a test segment.

One prompt per setup task, in the order of the Getting started steps. Replace what sits between braces, `{like this}`, with your own names. Reads change nothing; for every change your users could see, the assistant shows a preview and waits for your yes.

{% hint style="info" %}
**Use the names you see in Jimo.** The assistant finds experiences, segments and environments by their exact title. A convention such as `ADM 1.0 Create a project` makes every prompt below shorter. See [Working with your spec and your team](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/working-with-your-spec-and-your-team.md).
{% endhint %}

***

## Start: give it the context

#### Describe your product and your goal

```
I am setting up Jimo for {product name}. Our users log in at {app domain}.
They are {who your users are}. The goal of the first month is {one goal, with a number if you have one}.
Read the project and tell me what is already there: environments and their domains, what is live, what is in draft.
Do not change anything yet.
```

#### Check the workspace

```
List the environments of this project and their domains.
Flag any domain that contains https://, a path or a query string, and tell me what to type instead.
```

The fix itself is made in [Settings > Environments](https://help.usejimo.com/docs/settings/environments.md). See [Environments and domains](https://help.usejimo.com/docs/getting-started/your-workspace/environments-and-domains.md).

## Build from your spec

#### Gap analysis: spec against what is built

```
Read {name of the spec page} with your {Notion / Google Drive} tools.
Then read every experience whose name starts with {ADM}.
For each item of the spec, give me a table: built or missing, text differences, step order differences,
and what each button or checklist task launches compared with what the spec says.
Do not change anything yet.
```

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fez7qcFUHWZg9ePaOBKhz%2FA-07-gap-analysis.png?alt=media&amp;token=103452ba-ed6d-4a09-a011-be5f92e73ae9" alt="The assistant reads your request, your spec and your Jimo project, then returns a spec vs build table of item, status and gap: ADM 0 Welcome tour built, gap none; ADM Checklist built, 2 of 3 tasks; ADM 1.0 Create a project missing, not drafted; no change made yet"><figcaption></figcaption></figure>

#### Apply the fixes

```
Apply the fixes for {experience name} from the table: {texts / step order / what the buttons launch}.
Tell me what you changed, step by step.
```

A draft the assistant created, and that nobody edited in the dashboard, changes at once. A live experience, or a draft someone edited in the dashboard, is previewed first.

#### Draft a journey: checklist and tours

```
From the spec, draft the tours that are missing, one per checklist task, named {ADM 1.0}, {ADM 2.0}...
Then draft {ADM Checklist}: each task launches the tour with the same number,
and is marked done when that tour is completed.
The last button of {ADM 0 Welcome tour} opens the checklist.
```

Draft the tours first: a task can only launch an experience that exists. A task marked done on an event needs that event to exist in the project already; the assistant says so. See [Checklist and tours together](https://help.usejimo.com/docs/getting-started/create-your-first-experience/checklist-and-tours-together.md).

#### Pin a step to an element

On a page of your app where Jimo runs, open the browser console, run the line below on the element, and copy what it returns.

```javascript
jimo.push(["get", "anchor:capture", [element]])
```

Then:

```
Pin step {step name} of {experience name} to this element: {paste the capture}.
```

If the capture matches more than one element, capture something more specific, or ask your developer for a `data-jimo-id` on it. Details in [Pinning steps to your app](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md#pinning-steps-to-your-app).

#### Turn a hint into a one-step tour

```
Read the hint {hint name}. Draft a tour named {new name} with a single tooltip step,
the same title, text and button, pinned to this element: {paste the capture}.
Leave the hint as it is.
```

A hint stays one tooltip on its element; a tour can grow into a sequence later. Pause the hint once the tour is live, so users do not get both.

#### Translate

```
Which languages does {experience name} have? Translate it into {French, German}.
```

Each language written counts against your [monthly allowance](https://help.usejimo.com/docs/integrations/mcp/managing-access-usage-and-limits.md). To fix one wording by hand afterwards, ask for that field only. See [Multiple languages](https://help.usejimo.com/docs/build/multiple-languages.md).

## Prepare the handoff to your developer

#### The elements each step points at

```
For every experience whose name starts with {ADM}, list step by step:
the page, the element, the selector Jimo uses, and the confidence.
Put it in a table for my developer, and flag selectors that look generated
(hashed class names, numbered ids), so they can add a stable attribute on those elements.
```

Your developer adds a `data-jimo-id` with a unique value on the flagged elements (or a `data-testid` your team already uses), then you capture them again. See [Stable selectors on a dynamic front-end](https://help.usejimo.com/docs/getting-started/create-your-first-experience/stable-selectors-on-a-dynamic-front-end.md).

#### The attributes to send

```
Read {name of the attributes page} with your {Notion / Google Drive} tools.
Turn it into a handoff for my developer: key, type, example value, where the value comes from in our app.
Remind them that every set command goes before identify, and that dates are ISO-8601 strings.
```

The assistant does not read the attribute list of your Jimo project: it works from your document. The rules are in [Attributes and events](https://help.usejimo.com/docs/getting-started/install-jimo/attributes-and-events.md).

## Test and publish

#### A preview link

```
Send me a preview link for {experience name} on {environment name}.
```

The link opens the draft in your app without the dashboard and without publishing. It expires: ask for a new one when it does. See [Test safely](https://help.usejimo.com/docs/getting-started/publish-your-first-experience/test-safely.md).

#### Target a test segment first

```
Which saved segments exist, and how many users are in each?
Target {experience name} at {Test, me} and show me how many users it reaches.
```

The preview gives the number before you confirm. To keep some accounts out of a go-live, create a segment whose conditions leave them out, in [Users & Segments](https://help.usejimo.com/docs/analyze/users-and-segments.md), then target that segment.

#### Publish to one environment

```
Publish {experience name} to {Staging} only. Show me the preview first.
```

Publishing follows your plan's rules, exactly as in the dashboard. Check on your app with the Troubleshoot tool before you widen: see [Publish your first experience](https://help.usejimo.com/docs/getting-started/publish-your-first-experience.md).

#### Tag for review

```
Tag each of these experiences Needs review: {ADM 0 Welcome tour}, {ADM Checklist}, {ADM 1.0}.
Create the tag if it does not exist.
```

The assistant sets tags one experience at a time, so a long list takes a moment.

## Related

* [Set up with an AI assistant](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant.md)
* [Prompt library: routines](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/prompt-library-routines.md)
* [What to ask](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md), for more examples by permission
