Get Great Results: How to Prompt
How to prompt Respira for great results: the mental model, the great-results checklist, copy-paste starter prompts, per-builder notes, and fixes for common bad results.
Overview
This guide shows you how to prompt Respira for great results, plus a library of ready-made prompts. Most frustrating results ("it only made a basic layout", "it built one block of code", "the styles didn't apply") are not bugs. They are prompting and workflow gaps, and one extra sentence usually closes them.
These prompts work best when Respira is fully installed and configured. If you have not set things up yet, see the Installation and Configuration guides.
For more background, also visit the Introduction, Usage Guide, and Troubleshooting.
The mental model
Read this once. Everything else follows from it.
Respira lets an AI agent edit your live WordPress site through the page builder's own native tools. When you ask Claude or ChatGPT to change your homepage, it is not editing files or touching the database. It is calling Respira tools that speak your builder's language: Elementor widgets, Divi modules, Bricks elements, Gutenberg blocks.
- The builder is the language, and the agent has to speak it. A Divi page is a tree of Divi modules; an Elementor page is a tree of Elementor widgets. If the agent drops raw HTML into a builder page, the builder cannot read it and the page opens to a blank or broken canvas. This single mistake causes most bad results.
- One account per site. Name the site you mean when you have more than one connected.
- Snapshots protect you. Every edit creates a rollback point automatically, so it is safe to let an agent work on a real site.
- You describe outcomes, not markup. Say what you want ("make the hero headline punchier and the button green"). Let the agent pick the modules. You should rarely paste HTML, and you should rarely be asked to.
A useful way to picture it: Respira is a translator standing between your AI and your site. The AI speaks plain English to you and the builder's native language to the site. Bad results usually mean the translator was handed the wrong kind of input (raw code) or was not told which language the site speaks (which builder is active).
The great-results checklist
These habits separate a great result from a frustrating one. Most take one extra sentence.
- Prime the agent first. Before any real work: "Before we start, detect my builder, read my site, and use native builder modules only. Duplicate any live page before editing it." This is the single highest-leverage thing you can do.
- One site per request, and name it. "Edit the about page on clientco.com", not "edit the about page".
- Describe the outcome, not the HTML. "Add a three-card benefits section under the hero" beats pasting a block of
<div>s. - Let it duplicate or snapshot before touching a live page. For any published page, ask the agent to duplicate it first, edit the copy, and show you the preview before going live. This is SafeEdit.
- Never ask for raw HTML or code blocks when the builder has native modules. Ask for "a pricing table using the builder's native modules", not "the HTML for a pricing table".
- If a style "doesn't apply", it is unsupported on that builder, not a bug to retry. Pick a supported attribute or a different module. Retrying the same dropped write is the number-one source of wasted tokens.
- Read, then write. If you sense the agent is guessing, tell it to read the page first.
Tip
The plugin ships a one-click primer and a library of 20 ready-made prompts on the Prompts screen. The primer is the checklist above in one paste.
Copy-paste starter prompts
Tuned to produce the safe, native-first workflow. Copy, fill in the brackets, send.
First session (the primer)
Run this once at the top of any new conversation about a site.
Before we start, prime yourself for this site with Respira. Detect the active page builder and its version, read my site context, and list a few of my pages so you know the lay of the land. From here on, follow Respira's safe workflow: every page edit goes through the builder's native modules, never raw HTML; duplicate any live page before editing it; read the exact element before you change it. When you are ready, give me a one-line briefing of what you found.
Edit a page
On [page name or URL], change [what you want] using builder-native Respira tools only. Find the exact element first by its current text or by its type. If the target is ambiguous, ask me rather than guessing. Show me a preview before anything goes live.
Build a new page
Create a draft page called [title] using the active page builder. Use this structure: hero, trust proof, three benefit cards, process steps, FAQ, final CTA. Use native builder modules, not raw HTML. Mark placeholder copy clearly as draft. When done, give me the draft URL, the builder used, and anything that needs my review.
Redesign or improve an existing page
Improve [page] without redesigning it from scratch. Keep the brand colors, fonts, and layout intent. Strengthen the headings, spacing, and CTA placement using the builder's native settings. Make the smallest changes that improve readability and keep mobile working. Duplicate the page first and show me the preview.
Audit before you touch anything
Audit [page or my whole site] with Respira. Run site and builder context checks first, then inspect the homepage and my highest-value pages. Return a prioritized plan: quick wins under 30 minutes, medium tasks, deep tasks, and risks. Do not make any changes yet.
When the result is wrong
Plain-language fixes for the things people actually report.
| What you see | What happened | What to say next |
|---|---|---|
| "It only makes basic layouts" | The agent did not read the builder's full capabilities. | "Detect my builder, load its module schemas, then rebuild using richer modules (columns, cards, accordions), not just headings and text." Name the structure you want. |
| "It built one big HTML block" | The agent bypassed the builder with raw HTML. | "That is a code block, not a native page. Rebuild it using [builder]'s native modules only." Then re-prime. Common on Oxygen 6. |
| "The styles didn't apply" | The builder did not recognize that setting and dropped it. | "Use a supported attribute or a different module to get the same look." Do not retry the same write. |
| "Handshake loop / plan unavailable" | A connection or context step is failing. | "Run a connection diagnosis and tell me which layer is failing." Most are documented known issues with a quick fix. |
| "It burns tokens every time" | The agent is not carrying context between turns. | Prime once at the top of the session. The Prime-the-Agent skill also stores a per-site brief on the site itself for the next session. |
Tip
Click to copy: All prompts on this page have a copy button. Click any code block to copy the prompt to your clipboard.
Featured Prompt: Complete Homepage Redesign
This master prompt demonstrates how to leverage AI for a comprehensive homepage redesign. It combines research, design, SEO, AEO, performance optimization, and implementation into a single powerful workflow.
Info
Before using this prompt: Feed your AI assistant context about your brand by sharing relevant URLs, previous conversations, and brand guidelines. The more context you provide, the better the result.
Complete Homepage Redesign Prompt
Hey, I need you to redesign my homepage using everything you know about me and my brand.
First, analyze these resources to understand who I am and what I do:
- My current website: [YOUR_CURRENT_SITE_URL]
- My portfolio/work: [YOUR_PORTFOLIO_URL]
- My LinkedIn: [YOUR_LINKEDIN_URL]
- My GitHub: [YOUR_GITHUB_URL]
- Any other relevant URLs: [ADDITIONAL_URLS]
Based on this research, design a completely new homepage for [YOUR_DOMAIN] that:
**Design Requirements:**
- Super simple business card style layout
- Looks amazing on both mobile and desktop (mobile-first)
- Modern, clean aesthetic with intentional whitespace
- Fresh color palette that matches my current brand identity
- Use relevant images and logos you find on the pages I mentioned
**Performance Requirements:**
- Loads blazing fast (target < 2s load time)
- Optimized images with proper sizing and lazy loading
- Minimal CSS and JavaScript
- Core Web Vitals compliant (LCP < 2.5s, CLS < 0.1, INP < 200ms)
**SEO & AEO Requirements:**
- Proper heading hierarchy (single H1, logical H2-H6 structure)
- Schema markup for Person/Organization
- Semantic HTML structure for AI parsability
- Clear, scannable content with entity recognition
- FAQ section for featured snippet opportunities
- Meta description optimized for both search and AI engines
**Technical Implementation:**
Since you're connected to my site via Respira for WordPress MCP, please:
1. Create a duplicate of my current homepage first
2. Build the new layout using [DIVI/ELEMENTOR] builder
3. Include all custom CSS needed for the page
4. Make it production-ready
Output a complete implementation including:
- Full page structure with all modules
- Custom CSS for the page
- Any custom code modules needed
- Image optimization recommendations
Warning
Adapt this prompt to your reality: Replace all bracketed placeholders with your actual URLs and preferences. The more specific you are, the better the AI can serve you.
How to Use These Prompts
- Analyze first: Get the structure of the page before making changes.
- State your goals: Be clear about SEO, design, accessibility, or performance objectives.
- Use duplicates: Apply changes to a duplicate page for safe testing.
- Iterate: Make changes in small steps and review results in the audit log.
Best-Practice Workflow
Step 1: Get Your Page Structure
Get the structure of my homepage and show me what sections it has.
Step 2: Request Improvements
Analyze this page and suggest improvements for [YOUR_GOAL].
Replace [YOUR_GOAL] with: SEO, Design, Readability, Conversions, Performance, Accessibility, Mobile, or Engagement.
Step 3: Apply Changes Safely
That looks good, apply those changes to a duplicate page so I can review.
Comprehensive SEO Prompts
Full SEO Audit
Full SEO Audit
Run a comprehensive SEO audit on my homepage (page ID: [PAGE_ID]).
Analyze and report on:
1. Meta tags (title, description, canonical, robots)
2. Heading hierarchy (H1-H6 structure and keyword usage)
3. Content quality (word count, keyword density, readability)
4. Image optimization (alt text, file sizes, lazy loading)
5. Internal linking structure
6. Schema markup presence and validity
7. Mobile-friendliness indicators
8. Page speed factors affecting SEO
For each issue found, provide:
- Current state
- Recommended fix
- Priority level (critical/high/medium/low)
- Implementation steps
Then create an actionable plan to fix all issues, starting with critical ones.
... (remaining content unchanged)