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

# Jurni Prompt Library

> Copy-ready prompts for campaign creation, page replication, Figma, CRO, mobile, copy, offers, experiments, QA, and common growth workflows.

# Jurni Prompt Library

Use these prompts as **starting briefs**, not rigid formulas. Replace the bracketed fields, attach the real source material, and remove instructions that do not apply to your campaign.

For the reasoning behind the structure, read [Prompting 101](/academy/prompting-101).

## New campaign builds

### Build a cold-traffic product landing page

```text theme={null}
CONTEXT
This page is for first-time customers arriving from [Meta/TikTok/Google] ads.
Audience: [audience].
The campaign angle is: [angle].

GOAL
Move visitors from the campaign promise to understanding why [product] is relevant, then toward [primary action].

SOURCES
Use the attached ad, connected product, approved brand assets, and AI Knowledge.

BUILD
Create:
1. Hero that immediately continues the campaign promise.
2. 3 concise benefit points.
3. A short “how it works / why it is different” section.
4. Approved social proof.
5. Product / purchase section.
6. FAQ addressing [top objections].

KEEP
Do not invent claims, reviews, discounts, guarantees, pricing, or urgency.

MOBILE
Prioritize headline, primary proof, product visual, and CTA early in the page.
```

### Build a retargeting landing page

```text theme={null}
This page is for returning visitors who already know [brand/product] and are being retargeted after [previous interaction].

Build a shorter, more product-forward page.
Focus on:
- the main purchase reason
- approved proof
- the current offer
- objections that could still block purchase
- a clear purchase action

Do not repeat long introductory education that a first-time visitor would need.
Use the attached product and current approved offer.
```

### Build a Google-search landing page

```text theme={null}
CONTEXT
Traffic is coming from Google searches for [search intent / keyword theme].
The visitor is actively looking for [job-to-be-done].

GOAL
Answer that intent immediately and make it easy to evaluate [product].

BUILD
- Hero that directly answers the search intent.
- Clear explanation of how the product solves the job.
- Comparison / proof section if supported by approved information.
- Product section and FAQs.

Avoid ad-style hype or unrelated storytelling.
Do not introduce claims that are not in the supplied source material.
```

## Ad-to-page workflows

### Turn a Meta ad into a landing page

```text theme={null}
Use the attached Meta ad as the campaign brief.

Identify:
1. the hook
2. the primary promise
3. the audience implied by the creative
4. the strongest proof or product reason

Build a landing page that feels like the natural next step after the click.
The first screen should continue the same promise before introducing new information.
Use the attached product and approved assets.
Do not invent a new campaign angle.
```

### Build from a creator ad

```text theme={null}
Use the attached creator ad as the voice and message reference.

The landing page should feel consistent with the creator's recommendation without pretending the creator wrote content they did not provide.

Build:
- hero that repeats the creator's main reason for recommending the product
- short “why I use it / why it matters” section using only approved creator content
- product education
- proof
- purchase section

Keep the creator's tone natural and avoid turning the page into generic brand copy.
```

### Improve message match on an existing page

```text theme={null}
Review the attached ad and the current landing page.

Do not edit yet.
List the places where the first 25% of the page does not match:
- the ad hook
- the audience
- the promised outcome
- the product shown
- the offer
- the expected next action

Then propose the smallest set of changes that would make the transition feel continuous.
Prioritize hero and above-the-fold changes first.
```

## Reference and replication prompts

### Recreate a full page from a URL

```text theme={null}
Use [URL] as a structural and interaction reference.

Recreate the page flow using our brand, attached products, approved assets, and AI Knowledge.

Use the reference for:
- section order
- spacing and hierarchy
- interaction patterns
- pacing from education to purchase

Do not copy the reference brand's:
- logo or imagery
- testimonials
- claims
- pricing
- offer
- product names

Keep all customer-facing content specific to our brand.
```

### Recreate one section from a URL

```text theme={null}
Use [URL] as a reference for the [section name] section only.
Recreate the structure and interaction pattern using our brand styles and supplied content.
Do not copy content from any other section of the reference page.
Keep the rest of this Jurni page unchanged.
```

### Use a screenshot as a layout reference

```text theme={null}
Image 1 is a LAYOUT REFERENCE only.
Image 2 is the real product image to use.

Recreate the layout shown in Image 1 with editable Jurni content.
Use our fonts, colors, copy, and Image 2.
Do not use Image 1 as a flattened image in the finished section.
```

### Combine two references

```text theme={null}
Use Reference A for the page structure and shopping flow.
Use Reference B for typography, spacing, and visual tone.
Use our own product, copy, imagery, reviews, and offer.

Where the references conflict, prioritize:
1. our approved brand guidance
2. working Jurni purchase behavior
3. Reference A structure
4. Reference B styling
```

## Figma prompts

### Build from desktop and mobile Figma frames

```text theme={null}
Desktop Figma: [link]
Mobile Figma: [link]

These are two responsive versions of the SAME page.
Recreate them as editable Jurni sections.

Use the attached product where the design includes purchasing.
Preserve working form / purchase interactions rather than turning controls into static artwork.

Do not append the mobile frame as another page section.
Check that the implemented desktop and mobile versions match their respective frames.
```

### Build one section from Figma

```text theme={null}
Use this Figma frame for the selected [hero / comparison / testimonial / FAQ] section only: [link]

Match:
- hierarchy
- spacing
- typography scale
- media placement
- responsive intent

Keep the existing section's approved copy and current CTA / product behavior unless the Figma explicitly requires a different approved behavior.
Do not change other sections.
```

## Copy and messaging prompts

### Rewrite a hero for a specific audience

```text theme={null}
Rewrite only the selected hero for [audience].

Primary problem/desire: [problem].
Approved product reason: [reason].
Traffic source: [source].

Create:
- headline under [X] words
- one supporting sentence
- CTA label aligned with [action]

Keep the existing image, layout, product connection, and CTA destination.
Do not introduce new claims.
```

### Make copy easier to scan

```text theme={null}
Edit only the selected section.
Keep all factual meaning and approved claims.

Make it easier to scan by:
- shortening paragraphs
- using stronger subheads
- turning dense lists into 3–5 concise points
- removing repetition

Do not make the tone more aggressive or add urgency.
```

### Turn product features into benefits

```text theme={null}
Use the approved product facts below.
For each feature, explain the customer benefit in plain language.

Do not add any outcome that is not supported by the source.
Avoid generic phrases like “game-changing” or “revolutionary.”

SOURCE:
[paste approved product facts]
```

### Create an FAQ from real objections

```text theme={null}
Create an FAQ section using ONLY these customer objections:
1. [objection]
2. [objection]
3. [objection]
4. [objection]

Use the approved answers below as the factual source.
Keep answers concise and direct.
Do not create medical, legal, performance, or guarantee claims beyond the supplied wording.
```

## Layout and design prompts

### Improve a weak hero without changing the message

```text theme={null}
Redesign only the selected hero.
The current message is approved—do not rewrite it.

Improve:
- visual hierarchy
- spacing
- product prominence
- CTA visibility
- social-proof placement

Keep the headline, supporting copy, product, offer, and CTA action unchanged.
```

### Make a section feel more premium

```text theme={null}
Edit only the selected section.
“Premium” for this brand means:
- more whitespace
- fewer competing colors
- stronger type hierarchy
- larger, cleaner product imagery
- less decorative UI

Do not change the section's copy, content order, or interaction behavior.
```

### Simplify an overcrowded section

```text theme={null}
The selected section has too many competing elements.
Keep the core message and proof, but reduce visual noise.

Prioritize:
1. [primary idea]
2. [supporting proof]
3. [CTA if applicable]

Remove or de-emphasize secondary decoration and duplicated copy.
Do not remove required legal or offer information.
```

## Mobile prompts

### Fix only mobile

```text theme={null}
The desktop version is approved. Do not change desktop.

Fix only the mobile layout of the selected section:
- remove horizontal overflow
- stack elements in the order [order]
- use full-width CTA
- reduce side padding
- keep tap targets easy to use

Keep all copy, product choices, and button behavior unchanged.
```

### Make a comparison table mobile-friendly

```text theme={null}
Keep the desktop comparison table unchanged.
On mobile, convert it into stacked comparison cards.

Each card should clearly show:
- comparison criterion
- our product
- alternative

Keep all comparison wording exactly as approved.
Do not add new comparison claims.
```

### Improve mobile above-the-fold

```text theme={null}
Optimize the mobile first screen only.

The visitor should understand:
1. what the product is
2. the main campaign benefit
3. the strongest proof
4. what to tap next

Reduce anything that pushes those four items too far down the screen.
Keep desktop unchanged.
```

## Product and purchase-area prompts

### Restyle a product purchase section without changing behavior

```text theme={null}
Restyle the selected product / purchase section to match [reference].

KEEP
- connected product
- available variants
- subscription options
- default selection
- quantity behavior
- dynamic pricing
- current purchase action
- cart / checkout behavior

Change only the visual layout, copy hierarchy, spacing, and approved imagery.
Do not replace functional selectors with static buttons.
```

### Make subscription more understandable

```text theme={null}
Improve only the presentation of the existing subscription and one-time purchase choices.

Goal: make the difference easy to understand at a glance.
Use only the real selling plans, approved savings, and terms already available.

Do not create a subscription plan, discount, cadence, or savings amount that does not exist.
Keep the actual purchase behavior unchanged.
```

### Review a purchase section before launch

```text theme={null}
Review the selected purchase section.
Do not edit yet.

Check for:
- unclear variant labels
- unclear subscription vs one-time choice
- mismatched displayed price and offer copy
- weak CTA hierarchy
- mobile usability issues
- content that looks static but should be interactive

Separate visual recommendations from anything that requires verifying the real cart or checkout.
```

## Offer prompts

### Present an approved discount

```text theme={null}
The actual discount is already configured outside the page.

Update the selected section to PRESENT this approved offer:
[offer details]

Use the approved price / savings information provided.
Do not create or change discount logic.
Do not hard-code a promotional price in place of dynamic product pricing unless explicitly supplied as approved static copy.
```

### Build a gift-with-purchase campaign section

```text theme={null}
Create a section explaining this approved gift-with-purchase offer:
[qualification]
[gift]
[approved terms]

Make the qualification easy to understand before the shopper reaches the purchase section.
Do not change the actual gift or Shopify discount setup.
Include concise eligibility copy and avoid implying the gift is available when the qualification is not met.
```

### Explain free shipping clearly

```text theme={null}
Add a concise free-shipping message using this approved rule:
[rule]

Use plain language and keep the threshold visible.
Do not imply free shipping applies to regions, purchase types, or orders that are not covered by the supplied rule.
```

## Social proof prompts

### Improve testimonial presentation

```text theme={null}
Restyle only the selected testimonial section.
Keep every testimonial, name, rating, and attribution exactly as approved.

Improve:
- quote readability
- visual hierarchy
- mobile layout
- distinction between customer quote and surrounding brand copy

Do not rewrite testimonials or add review counts.
```

### Create proof hierarchy

```text theme={null}
Review the page's existing approved proof.
Do not invent new proof.

Recommend where each proof type should appear:
- ratings / review count
- customer quotes
- creator endorsement
- press / awards
- product-specific evidence

Prioritize proof closest to the claim it supports rather than collecting all proof in one section.
```

## Page-type prompts

### Build an advertorial

```text theme={null}
Build an advertorial-style landing page for [audience] around this approved angle: [angle].

Flow:
1. editorial-style headline
2. problem / tension
3. why common alternatives fall short
4. discovery or insight
5. introduction of [product]
6. approved proof
7. transition to purchase
8. FAQ

Keep the opening educational rather than sales-heavy.
Do not disguise paid promotional content as independent journalism.
Use only approved claims and proof.
```

### Build a listicle

```text theme={null}
Build a “ [X] reasons why [audience] choose [product / approach] ” landing page.

Each reason should:
- have one clear takeaway
- use approved evidence or product truth
- be visually skimmable
- move the reader closer to the purchase decision

Avoid repeating the same benefit in different words.
End with a clear product and purchase transition.
```

### Build a founder-story page

```text theme={null}
Build a founder-story landing page using the attached founder material.

The story should answer:
- what problem the founder experienced or observed
- what was missing from existing options
- what principle guided the product
- why the product is different
- why the customer should care

Keep the founder's approved wording and facts.
Do not invent quotes, life events, credentials, or origin details.
Transition from story to product naturally.
```

### Build a creator landing page

```text theme={null}
Build a landing page for traffic from [creator].
Use the attached creator ad / brief.

Keep the creator's main recommendation angle in the hero.
Use approved creator quotes exactly as supplied.
Then transition into brand-owned product education, proof, and purchase.

Do not make the creator appear to endorse claims they did not make.
```

## CRO and experiment prompts

### Create a controlled hero test

```text theme={null}
This is an A/B test variant.

HYPOTHESIS
If we [change], then [audience] will be more likely to [behavior] because [reason].

CHANGE ONLY
The selected hero message.
Use this approved alternative angle: [copy / angle].

KEEP IDENTICAL
- product
- offer
- purchase behavior
- page structure below the hero
- CTA action
- tracking
- all unrelated copy

Do not make additional “optimization” changes.
```

### Create an offer-framing test

```text theme={null}
This is an experiment variant testing OFFER PRESENTATION, not offer economics.

Keep the actual product, discount, price, gift, and purchase behavior unchanged.
Change only how the approved offer is explained and visually prioritized in [section].

Variant angle: [new framing].
Do not change any Shopify or cart logic.
```

### Review a page for test ideas

```text theme={null}
Review this page and identify potential test hypotheses.
Do not edit the page.

For each idea provide:
- observed problem
- customer decision it may affect
- proposed single variable to test
- primary metric that would indicate improvement
- risk of confounding the result

Prioritize 5 ideas by expected impact and confidence.
Avoid suggesting cosmetic tests with no clear customer decision behind them.
```

### Turn a result into the next test

```text theme={null}
Here is the experiment result and original hypothesis:
[result]
[hypothesis]

Do not assume the winning variant proves why it won.
Give me:
1. what we can reasonably conclude
2. what remains uncertain
3. what should be preserved
4. 3 logical next hypotheses

Prioritize the next test that builds on the strongest evidence without changing multiple major variables at once.
```

## QA prompts

### Pre-launch marketing review

```text theme={null}
Review this page against the attached campaign brief.
Do not edit yet.

Check:
- message match with the campaign
- unsupported or inconsistent claims
- wrong product / offer references
- unclear primary CTA
- missing objection handling
- weak social-proof placement
- mobile hierarchy
- links or actions that look inconsistent

Return a prioritized checklist: BLOCKER / SHOULD FIX / OPTIONAL.
```

### Copy consistency review

```text theme={null}
Review all visible customer-facing copy on this page.

Flag:
- conflicting product names
- inconsistent offer wording
- inconsistent subscription terminology
- mismatched numbers or percentages
- repeated claims that use different wording
- placeholders or generic AI copy

Do not rewrite yet. Give me the exact sections that need correction.
```

### AI-slop cleanup

```text theme={null}
Review this page for generic AI-style language.

Flag phrases that are:
- vague
- overhyped
- repetitive
- unsupported
- not specific to this product or audience

For each flagged phrase, suggest a tighter alternative using only the approved product facts and brand voice.
Do not introduce new claims.
```

### Final experiment-variant check

```text theme={null}
Compare this variant with the control before launch.

Confirm the intended test variable is the only meaningful difference.
Flag any accidental changes to:
- product
- price / offer
- purchase options
- CTA action
- page structure outside the hypothesis
- tracking-related content

Do not edit. List differences first.
```

## Correction prompts

### Tell Jurni exactly what is still wrong

```text theme={null}
KEEP
[what is now correct]

FIX ONLY
[the remaining issue]

DO NOT CHANGE
[working elements]

The current result is attached as CURRENT.
The target is attached as DESIRED.
```

### Recover after an over-broad edit

```text theme={null}
The last edit changed more than requested.

Keep the intended change to [target].
Restore the previous behavior / content for:
- [item]
- [item]
- [item]

Do not make additional design improvements.
After the correction, summarize exactly what remains different from the prior version.
```

## Build your own prompt

Copy this reusable template:

```text theme={null}
CONTEXT
[Traffic source, audience, campaign angle, what the visitor already knows]

GOAL
[The one outcome this page/section should support]

SOURCES
[Products, ads, media, files, URLs, Figma, AI Knowledge]

CHANGE
[Exactly what to build or edit]

KEEP
[Everything that should remain unchanged]

BEHAVIOR
[What buttons, selectors, forms, or purchase controls should do]

RESPONSIVE
[Important mobile and desktop differences]

DO NOT
[Claims, content, or behavior Jurni must not invent/change]

VERIFY
[What to review before the task is complete]
```

## Continue learning

* [Prompting 101](/academy/prompting-101)
* [Turn an ad into a landing page](/academy/playbooks/ad-to-landing-page)
* [Run your first A/B test](/academy/playbooks/first-ab-test)
* [Browse all playbooks](/academy/playbooks)


## Related topics

- [Jurni Guides](/guides.md)
- [Prompting best practices](/building-funnels/ai-chat-prompts.md)
- [Copy-ready prompts for Jurni](/build/prompt-library.md)
- [Prompting 101: get better results from Jurni AI](/academy/prompting-101.md)
- [Launch your first Jurni campaign](/academy/start/first-campaign.md)