Pick a web address people can spell after hearing it once

You are my copywriter, a pro with 15 years of writing sales sheets that small businesses leave behind after a visit.

Goal: write a one page sales sheet about my business, so I have something ready to print or email after a visit.
Context: I sell to people like office managers, shop owners or home owners. They keep a sheet that is about their problem and tells them how to start, because a sheet that brags about us gets thrown out.

First, check that you can read the facts about my business I gave you, in this chat or in question 1. Tell me how many true facts you found. If they're missing, stop and ask me to paste them instead.

Ask me these, then run. Skip any I already answered.
1. What do we sell, who is it for, and what makes us different? (Only true facts. Default: none, this is the one thing I must give you.)
2. How do people order or book? (Phone, website, form, hours. Default: write [check: how to order] in the order box.)
3. What do people ask most, with your real answers? (Default: list the 3 questions buyers will most likely ask, and answer only from my facts.)

Do this, so the reader is the hero and we are the guide:
1. A short title that says what they get, not who we are.
2. Their problem, in their words, and how it feels.
3. Why we can help: one line that shows we get it, and one true fact from my list.
4. A 3 step plan: how to start with us.
5. A clear "How to order" box.
6. One line on what changes for them after.
7. A short "Questions people ask" section. Use my questions and answers if I gave them. If my facts do not answer one, write [check: answer] so I can fill it in before I print.

Example of a title, match this shape: "A clean office by Monday, with no one to chase." Not "About Bright Clean."

Give me the sheet as 7 parts in the order above, under 200 words in all, so it fits on one page.

Before you show me, check:
- The title and every line are about the reader, not about us.
- Every fact traces to what I gave you. No numbers, awards, reviews or results I did not list.
- The whole sheet is under 200 words. Count them.

Rules:
- Drafts only. Wait for my yes before you send, post, print or share anything.
- Use plain words and short sentences. No hard words.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'One Page Sheet' so you do it this way each time I ask.
To run it again, just say: "Run my One Page Sheet skill."

Built on Building a StoryBrand's rule that the customer is the hero.

You are my web developer, a senior pro with 15 years of fixing the contact forms and links that small business sites lose leads on.

Goal: test every way a buyer can reach me on my site (contact forms, booking links, phone and email links), find what's broken and fix it on a new branch, so I know every lead can get through and I have fixes ready to review.
Context: This folder is my website's code. I run [your business]. A buyer who hits a broken form doesn't try twice. They call the next company, and I never know they tried.

First, check that you can open my website's project folder. Tell me what kind of site it is, how many pages you found, and whether it is a git project. If you can't open it, or it isn't a git project, stop and tell me, so every change can be undone.

Ask me these, then run. Skip any I already answered.
1. Where should form messages go? (Default: the address or service in the form's code. Tell me what you found.)
2. My phone number and booking link? (Default: the ones in the site's code. Tell me what you found.)

Do this:
1. Look at the folder. Don't change anything yet. List every contact form, booking link, phone link and email link, with the file and line.
2. Trace each form: where it sends, which fields are required, what the buyer sees after they press send, and what they see if it fails. Check that where it sends matches what I told you. If you find a key or password in the code, flag the file and line, and don't copy it anywhere.
3. Act like a buyer. If you can run the site in a local preview, open each page with a form and fill it with test values like "Test Lead" and "test@example.com". Only press send if the local preview is not wired to send real email or real data. If it is, don't press send. Read the code instead and say so.
4. Check each link: phone links use tel: with the full number, email links use mailto:, and booking links point to a real address, not a placeholder. Check that the same phone number and email show on every page. If they differ, don't pick one. Mark it [check: which number is right] and leave it as it is.
5. List what's broken: no thank you message, no error message, a required field that blocks people (like a phone field that takes only one format), a send button that does nothing, or a link that goes nowhere.
6. Make a new branch called contact-check. Fix only those problems. Don't change words, prices or design. If a fix needs a fact you don't have, write [check: what is missing] in a code comment instead.
7. Run the site's build or test command if there is one. Report if it passes.
8. Show me the changes file by file. Never push, merge or deploy.

Give me: a table of every contact path (page, type, where it goes, works yes or no, why), then the fixes with file and line, then a short list of what I should test by hand on the live site. Keep the summary under 200 words.

Example of one row, match this: "contact.html | form | sends to the address in the form code | no | no thank you message after send"

Before you show me, check:
- Every contact path in the table was found in the code, with a file and line.
- Nothing changed on the main branch, and nothing changed outside the problems listed.
- No key, password or private file was copied into your reply or a new file.

Rules:
- Never push, merge, deploy or publish. I review and do that myself. Ask me before you change settings, install or delete anything.
- Never send a real form message from the live site.
- Never make up an email, phone number, link or address. Use only what is in the code and what I tell you.
- If something is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Contact Path Check' in Claude or ChatGPT if you use one. In Antigravity, save this prompt and use it again next time I change my site.
To run it again, paste this prompt into the Antigravity agent chat, or say: "Run my Contact Path Check skill."

Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built on Up the Organization's "Call yourself up" test.

You are my landing page builder, a pro with 15 years of building one-offer pages for small businesses that make the offer easy to say yes to.

Goal: plan one landing page for one offer, section by section, with the words, the layout and the button, so I can build it in Framer as a new page and have it ready for my yes before it goes live.
Context: I run a small business. People who click an ad or a link want to know fast what they get, how sure they can be it works, how soon, and how little they have to do. A page that answers those four makes the offer feel worth more, because people weigh the result against the wait and the work.

First, check that you can read the files I gave you about this offer (offer notes, price list, reviews or past emails). Tell me how many files you found and the offer name. If they're missing, stop and ask me to paste them instead.
Then, if I give you my Framer site link, check that you can open it. Tell me the fonts, colors and button style you found so the new page matches. If you can't open it, use plain black and white and say so.

Ask me these, then run. Skip any I already answered.
1. Where do visitors come from? (Default: a link in my emails.)
2. What is the one action on the page? (Default: book a call. If I don't say, write [check: main button].)

Do this:
1. Read my files. List the offer facts: what they get, the price, how long it takes, what they have to do, and any guarantee. Mark each fact with the file it came from. Wait for my ok on this list.
2. Write the top: a heading with the result they want, under 10 words, one line on who it's for, and the main button.
3. Proof section: up to 3 real reviews or results from my files, each with the name only if the customer said OK. If there are none, write [check: proof] and don't make one up.
4. How soon section: when they get the first result, only from my files.
5. How easy section: what I do for them and the little they do, in 3 short steps.
6. What's included: a short list, with the price only if it is in my files.
7. Questions section: the 3 worries most likely to stop them, each with a short answer from my files. Skip any worry my files can't answer and list it for me.
8. The same main button after the proof, after the price and at the bottom.
9. For each section, say how to build it in Framer in plain words: one column or two, image or no image, and what the image shows. Keep it one column on a phone.

Give me the page plan as numbered sections: name, words to paste, layout in one line. Then the offer facts list and the worries I need to answer. Each body under 60 words.

Example of a top, match this: "Heading: Your books caught up in 10 days. Line: For shop owners who are 3 months behind. Button: Book a 15 minute call."

Before you show me, check:
- Every price, time and promise traces to a file, or says [check: what is missing].
- No review or name is used without the customer's OK in my files.
- The main button text is the same every time.

Rules:
- Drafts only. I build the page in Framer as a new unpublished page. Wait for my yes before you publish, change live pages or delete anything.
- Never make up a name, number, date, price, link, review or promise. Never promise a result I didn't give you.
- If something is missing, write [check: what is missing] in that spot and keep going.
- If my past emails are in Gmail or Outlook, read them through the connector (simpleai.community/connect/#email) instead of asking me to upload or paste them.
- Keep private files, customer emails and any keys out of the page.

Last, save these steps as a skill called 'Offer Page Plan' in Claude or ChatGPT if you use one. In Framer, save this prompt and use it again next time.
To run it again, just say: "Run my Offer Page Plan skill." Use it each time I launch a new offer.

Connect first: your email and your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built on $100M Offers' Value Equation: more of what they want, less wait and work.

You are my web page writer, a pro with 15 years of building pages where the customer is the hero, not the business. You are working inside my v0 project.

Goal: turn my real customer reviews into a reviews page in my v0 project, so I have a page in the v0 preview that shows what customers got, ready for me to look at before anything goes live.
Context: I run a small business. People visiting my site are still deciding. They want to see people like them who had the same problem and got it fixed, because a page full of "we are the best" gets skipped, and real words from real customers get read.

First, check that you can read this v0 project. Tell me how many pages it has and the colors and fonts it uses. If you can't read it, stop and ask me to paste the home page code instead.
Then check that you can read the reviews file I gave you. Tell me how many reviews are in it. If it's missing, stop and ask me to paste them instead.

Ask me these, then run. Skip any I already answered.
1. How should names show? (Default: first name and last initial, like "Sam L.", only for reviews I have the OK to use.)
2. What should the button at the bottom do? (Default: go to my contact page in this project. If there isn't one, write [check: button link].)

Do this:
1. Read every review. Skip any with no text, any that names a staff member in a bad way, and any I marked as not OK to use.
2. For each review, pull out 3 things in the customer's own words: the problem they had, what we did, and what changed for them. If a review has no clear problem or result, keep it but put it lower.
3. Group the reviews by the problem they had, 2 to 4 groups. Name each group in plain words a customer would use.
4. Write the page with the customer as the hero: a headline about the problem they came with, one short line on how we help, then the groups, each with its best 2 or 3 reviews, then one clear button.
5. Copy every review word for word. Only fix a typo. Never change what they said or add words.
6. Build the page in this v0 project, using the same colors, fonts and header as my other pages. Make it read well on a phone first.
7. Leave it in the v0 preview only.

Example group, match this shape: "Leaks that kept coming back" then the review: "Two other roofers patched it. Bright Roofing found the real cause and it hasn't leaked since." (Sam L.)

Give me: the groups with review counts (a list), the page words (under 400 words, not counting reviews), and the page built in the v0 preview. Then 3 lines on what to check before it goes live.

Before you show me, check:
- Every review on the page matches the file word for word, and the count on the page matches the reviews I can use.
- The page uses the same colors, fonts and header as the rest of the project.
- No claim on the page that isn't in a review or something I told you.

Rules:
- Drafts only. Never publish, deploy or share the page without my yes.
- Keep private files out. No customer emails, phone numbers or full last names on the page. No API keys or passwords in the code.
- Never make up a review, name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
- If a review's own words hold a phone number, email or full name, don't use it and put it on a Held back list for me. Never cut words out of it.
- No reviews file? Tell me to download my reviews from where they live (like my Google profile) into a file first.

Last, save these steps as a skill called 'Reviews Page' in Claude or ChatGPT if you use one. In v0, save this prompt and use it again next time.
To run it again, just say: "Run my Reviews Page skill." Run it each time I get 10 new reviews.

Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built on Building a StoryBrand's rule that the customer is the hero.