> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getjurni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompting best practices

> Write precise Jurni AI requests for page creation, section edits, responsive design, Figma references, and Buy Boxes, with clear constraints and verification.

Use this Help Center page for the **quick product workflow**: what context you can attach to Jurni AI, how to scope an edit, and how to avoid changing working behavior.

For the complete marketer course—with the full prompting framework, examples, correction techniques, campaign structures, and copy-ready prompts—go to [**Academy: Prompting 101**](/academy/prompting-101) and the [**Jurni Prompt Library**](/academy/prompt-library).

A good prompt is a useful creative brief, not a technical specification. Tell Jurni **what you want to achieve, which source material to use, what to change, and what to keep**.

Start with the quick pattern below. Use the rest of this guide when you are building a new campaign, working from references, or making a more complex edit.

## A prompt you can use immediately

```text theme={null}
Create a landing page for [product] aimed at [audience] arriving from [ad or channel].
The main action is [add to cart / choose a subscription / visit another page].
Use [attached product, approved copy, images, or reference].
Include [the sections this campaign needs].
Keep [brand requirements and existing purchase behavior].
Do not invent reviews, claims, prices, or discounts.
```

For a small edit, one sentence is enough:

> In the selected FAQ section, replace the second answer with the copy below. Keep the other answers and the layout unchanged.

## 1. Give the campaign context

For a new page, describe the audience, the message that brought them there, the product or offer, and the action you want them to take. A visitor discovering your brand from an ad may need different information from a returning customer comparing purchase options.

**Too vague:** “Make a high-converting supplement page.”

**More useful:** “Build a page for first-time customers arriving from the attached morning-routine ad. Use the attached product and approved benefits. Explain how it fits into their routine, answer the supplied questions, then let shoppers select their purchase option.”

An objective such as improving conversion helps set direction. It is not a promise that a generated page will achieve a particular uplift. Use [experiments](/experiments/what-are-experiments) to evaluate a change.

## 2. Attach the right source material

Use the attachment options available in Jurni chat to supply products, images, files, ads, Figma links, or web references. A product name typed into a prompt is less precise than selecting the correct connected product when the product attachment is available.

| Source                          | Tell Jurni how to use it                                          |
| ------------------------------- | ----------------------------------------------------------------- |
| Connected product               | Use its real product choices and purchase data.                   |
| Approved copy or brand guidance | Treat this as the approved wording and factual source.            |
| Ad creative                     | Carry its message and audience angle into the page.               |
| Layout screenshot               | Use the arrangement and styling as a reference.                   |
| Product photograph              | Place this actual asset in the page.                              |
| Figma frame                     | Follow this design for the named screen size.                     |
| Web page                        | Use the specified section, visual style, or shopping interaction. |

### Reference images are not content images

Label what each attachment is for. Otherwise a picture of a layout can be mistaken for an image to place inside the page.

> Image 1 is a layout reference. Image 2 is the product photo to use in the hero. Recreate the arrangement using editable content; do not use the layout screenshot as the finished section.

### Separate visual design from interaction

A screenshot cannot explain everything a selector or purchase button does. Describe the behavior separately.

> Use the first reference for the bundle-selection steps and the second for typography and spacing. Shoppers should choose \[approved items] before continuing. Keep the existing cart connection and use the attached products.

For Figma, provide **Desktop: \[frame link]** and **Mobile: \[frame link]** as two versions of the same page. See [Build from Figma](/building-funnels/figma-file).

## 3. Name the part that should change

Select the intended section or element and check the context attached to your request. Then name that area in the prompt.

> Edit only the selected hero. Put the image beside the text on desktop. Keep the mobile stack, all copy, the CTA destination, and every section below it unchanged.

For a larger build, it helps to work in stages: establish the page structure, refine the content and visual design, connect the purchase behavior, then test. Do not ask for a complete rebuild when only one crop or spacing value is wrong.

## 4. Protect the working parts

State what must remain unchanged, especially on a nearly finished page. Useful constraints include the approved copy, selected product, variant choices, purchase type, quantity, button destination, and sections outside the requested area.

> Restyle this Buy Box to match the reference. Keep its products, available variants, subscription choices, default selection, quantities, discounts, and cart action unchanged. Keep the controls functional rather than replacing them with static artwork.

<Warning>
  Check whether you are editing a Global Section or shared product content. A prompt saying “only this page” is not a substitute for [detaching a global instance](/build/global-sections) when an independent version is needed.
</Warning>

A displayed discount does not create a checkout discount. Adding a subscription label does not create a valid subscription plan. Use [purchase options](/building-funnels/product-purchase-options) and [offers](/commerce/offers-overview) for the corresponding setup.

## 5. Describe mobile and desktop outcomes

Say what should happen at each screen size instead of simply asking for “responsive design.”

> On mobile, stack the image above the text and make the button full width. On desktop, keep the existing two-column layout. Preserve the product selection and button action on both sizes.

Jurni's base/mobile editing mode is **Editing All Sizes**; desktop can have separate overrides. Check both views after an AI edit. See [Desktop and mobile](/build/desktop-mobile).

## 6. Review one meaningful change at a time

Check the result before sending the next instruction. When it is close, describe the remaining mismatch rather than repeating the whole brief.

**Less useful:** “Still wrong. Fix it.”

**More useful:** “The new layout is right. The image still crops the bottle cap on mobile. Keep the layout and copy; change only the crop so the full bottle is visible.”

A screenshot of the current problem can help. Label it **Current result**, and label the target **Desired result**. Explain the difference that matters.

For a straightforward deletion, reordering, or exact text replacement, direct [editor controls](/building-funnels/funnel-editor) may be simpler than another prompt. Use AI for changes that are easier to describe than make manually.

## 7. Keep the conversation focused

Continue the same chat when refining one task. Start a new chat when switching to an unrelated campaign or when old instructions conflict with the new brief. Supply the important context again rather than assuming a fresh thread contains the previous discussion.

Chat history, Undo/Redo, and published versions do different jobs. Opening an old chat does not restore an old design. Use [chat history](/build/chat-history), [Undo/Redo](/build/undo-redo), or [version history](/build/version-history) for the appropriate task.

## 8. Verify the page before launch

Review the changed area and the parts that were meant to stay unchanged. Check approved claims and pricing, both screen sizes, product choices, links, and the final cart or checkout. Then save or publish deliberately.

<Note>
  An AI response saying an edit is complete is not a substitute for testing it. Use the [pre-launch checklist](/building-funnels/qa-checklist), including the actual published destination and campaign link.
</Note>

## Common prompting problems

<AccordionGroup>
  <Accordion title="Jurni changed more than I intended">
    Name the exact target, remove unrelated requests, and list what must remain unchanged. Check whether the selected content is shared. Recover with the appropriate editor history control before making the next edit when necessary.
  </Accordion>

  <Accordion title="The design matches, but buying does not work">
    A visual reference does not establish commerce behavior. Confirm the connected product, available variants, purchase plan, quantity, and button action. Test the actual cart item, not just the design.
  </Accordion>

  <Accordion title="The reference and the brand guidance disagree">
    Set priorities: for example, “Use the reference for layout, but keep our approved copy, fonts, colors, and product imagery.” Do not leave Jurni to guess which source wins.
  </Accordion>

  <Accordion title="The request keeps producing generic results">
    Replace broad adjectives with concrete instructions: which section, what arrangement, what copy, which asset, and which next action. Include approved source material instead of asking Jurni to invent proof.
  </Accordion>
</AccordionGroup>

Never paste private API keys, passwords, or customer personal information into a creative brief. Use approved assets and real testimonials, and do not request invented results or scarcity.

## Continue

* [Copy-ready prompt examples](/build/prompt-library)
* [Build your first page with AI](/build/ai-campaign-workflow)
* [Edit a page with AI](/build/ai-editing)
* [Set up AI Knowledge](/getting-started/setup-ai-knowledge)


## Related topics

- [Add a review widget to a page](/integrations/review-widgets.md)
- [Edit pages and sections with AI](/build/ai-editing.md)
- [Build a campaign page with AI](/build/ai-campaign-workflow.md)
- [Setting Up AI Knowledge in Jurni](/getting-started/setup-ai-knowledge.md)
- [Build from Figma references](/building-funnels/figma-file.md)