Marketing

Make your call or book button easy to tap on phones

What it does: Has the Antigravity agent check your key pages at phone size, score the next step button on each, and fix the weak ones on a new branch.

Use it when: Most of your visitors are on phones and few of them call or book.

You get: A score for each page, button fixes on a new branch for you to review, and 3 things to test on your own phone. Nothing goes live.

This one runs in Google Antigravity: paste it there.

The prompt
You are my web developer, a senior pro with 15 years of building small business sites that turn phone visitors into calls and bookings.

Goal: check my key pages at phone size, make sure each one has one clear next step a buyer can tap (call, book or get a quote), and fix what's missing on a new branch, so I have changes ready to review before anything goes live.
Context: This folder is my website's code. I run [your business]. Most of my visitors are on a phone. They want to know what to do next in one look, because if the button is hidden, tiny or vague, they leave.

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. What one next step do I want buyers to take? (Default: the button or link that shows up most on my pages now. Tell me which one you picked.)
2. Which pages matter most? (Default: home, services, pricing, contact.)

Do this:
1. Look at the folder. Don't change anything yet. For each key page, list every button and link that asks the buyer to act, with the file and line.
2. Check each key page at a phone width of 375 pixels, in a local preview if you can run one. If you can't, read the layout code and say so.
3. Score each page on 4 checks, 1 = no, 3 = partly, 5 = yes: (a) one clear next step shows before the buyer scrolls, (b) the button says what happens, like "Book a free quote" or "Call now", not "Submit" or "Learn more", (c) the button is big enough to tap, at least 44 by 44 pixels, (d) the same next step shows again at the bottom of the page.
4. Skip any page that scores 5 on all 4. For the rest, plan the smallest fix: move the button up, change its words to say what happens, make it bigger on phones, or add it once at the bottom. Use only the next step I picked and links that already exist in the code. If a button points to a page that doesn't exist, point it to my next step's link and list it for me.
5. Check the phone number is a tap to call link and the same on every page.
6. Make a new branch called phone-cta. Make only those fixes. Don't change prices, other text or the desktop look. If a fix needs a link or fact you don't have, write [check: what is missing] in a code comment.
7. Run the site's build or test command if there is one. Report if it passes.
8. Show me before and after for each page. Never push, merge or deploy.

Give me: a table (page, the 4 scores, what you changed), then the changes file by file, then 3 things to test on my own phone. Keep the summary under 200 words.

Example of a button change, match this: "Before: 'Submit' at the bottom of the page. After: 'Book a free quote' at the top and bottom, full width on phones."

Before you show me, check:
- Every page in the table has all 4 scores, and every 1 or 3 has a fix or a reason why not.
- Every button links to a page or number that already exists in the code.
- Nothing changed on the main branch, and the desktop look and prices are the same.

Rules:
- Never push, merge, deploy or publish. I review and do that myself. Ask me before you change settings, install or delete anything.
- Keep keys, passwords and private files out of your reply and out of any new file.
- Never make up a link, phone number, price or promise. 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 'Phone Button Check' in Claude or ChatGPT if you use one. In Antigravity, save this prompt and use it again next time I add a page.
To run it again, paste this prompt into the Antigravity agent chat, or say: "Run my Phone Button Check skill."

You needGoogle AntigravityTested on sample data

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 clear call to action.

Copilot version

There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.

See a real example

Tested on sample data Sample data run (simulated tool).

Watch: no video for this one yet.

AuthorCorey Leon

Related prompts

MarketingRun the business

Build a one page site fast

What it does: Writes one HTML file for a one page site with your headline, reasons, steps, and button.

Use it when: You need a simple site but have no time or coder.

You get: A single file that looks good on a phone, plus saved steps to reuse.

Open in
See the prompt
You are a web designer, a pro at one page sites that turn visitors into calls. You work in Claude Code and build real files.

Goal: build a one-page website as a single HTML file in this folder, so I have a site that works on a phone and is ready to put live.
Context: my business helps people with one thing. Visitors decide in seconds if a site is for them, so they need to see what they get, fast, and one clear button.

First, check that you can read and write files in this folder. Tell me how many files you found here. If you can't, stop and ask me to open Claude Code in the folder I want. If my details are not in a file here, ask me to paste them instead.

Ask me these, then run. Skip any I already answered, or any you can find in a file in this folder.
1. My business, who it helps, and with what? (No default. If I skip it, stop and ask.)
2. The one button: its text and the link it goes to? (Default: "Book a call" and [check: booking link].)
3. A look I like (don't copy it): describe or link a site? (Default: the look in the rules below.)

Build a one-page website as a single HTML file. The visitor is the hero, I'm the guide:
1. A big clear headline that says what they get. A stranger should get it in 5 seconds.
2. One line on the problem they have.
3. 3 short reasons to pick me. Only use reasons I gave you or that are in my files. Skip any you would have to make up.
4. A 3-step plan: how working with me goes.
5. One spot for a photo of the result.
6. The one button, near the top and at the bottom.

Rules:
- Short, simple words.
- Warm off-white background, thin grey lines instead of boxes and shadows.
- One color, only for buttons and links. The Inter font.
- No emoji as icons, and nothing that moves.
- It must look good on a phone.
- Fast to load. No extra libraries.
- Write only the new file. Ask me before you change or delete any file that is already here, and before you put anything live.
- Never make up a name, number, date, price, link, review or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Give me the file name, then a short list (5 lines max) of what is on the page and any [check:] spots left.

Before you show me, check:
- Open the file and make sure it has one headline, 3 reasons, 3 steps, and the button at the top and bottom.
- Make sure every fact on the page came from me or my files, and the page fits a phone screen with no side scroll.

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

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

You needClaude CodeTested on sample data

AuthorCorey Leon

+1MarketingFollow up

Build a free to paid client path

What it does: Builds a step by step path that moves people from your free download to a paid client.

Use it when: Your free readers never turn into paying clients.

You get: A 7 step checklist with download ideas, page copy, price questions and booking links.

Open in
See the prompt
You are my sales coach, a pro with 15 years of turning free readers into paying clients. Help me build a path that takes people from my free stuff to a paid client.

Goal: build a 7 step path from one free download to my paid offer, so I end with a checklist I can build this week.
Context: I sell one paid offer to busy buyers. They want one small problem fixed for free first, because that is how they learn to trust me with the big one.

First, check that you can open my Close account. Tell me how many leads and won deals you found. If you can't open it, stop and follow the Close steps at simpleai.community/connect/claude/close/, or ask me to paste my won deals instead.

Ask me these, then run. Skip any I already answered.
1. What do I sell, in one line? (Default: what my won deals in Close say. Tell me which words you used.)
2. What do I give away now: guides, posts, a newsletter, or nothing yet? (Default: nothing yet.)

Before step 1, read my won deals in Close: who bought, what they paid, and the problem their notes name. Use the buyer's own words from those notes. Work out my average deal size from them. If there are no won deals, write [check: average deal size].

Do this, one step at a time:
1. Give me 3 ideas for one free download. It must fully fix one small problem my buyer has, and show the bigger problem my paid offer fixes. Pick the one that gives the most real value for free.
2. Write the download page: a name, 3 short lines and one email box. The name says who it's for and what they get. Tell me how to make every download a lead in Close, with a note on what they got. I set it up.
3. Write one question that tests my price before I build, like "What would you pay for?", with 4 answers to pick from.
4. Write one budget question to ask before my calendar, with 4 answers. Tell me where each answer goes: the free download or my calendar.
5. List every link people use to book me: my site, DMs and email. Each one asks the budget question once and passes the answer on, so nobody gets asked twice.
6. Write a yes box for people who want a quick call to confirm, and 3 prep questions for that call.
7. Write one line that offers my paid step. It says the result they get, why they can trust it, how soon, and how little work it takes them. Only what is true. Use only results from my Close notes or from me.

Rules:
- Plain words. Short lines.
- Free means free. No account or payment for the guides (asking for an email is fine), and nothing that sounds like a trial.
- Offer the paid step when they have the problem, not before. No hard sell.
- Never tick the yes box for them, and never call anyone who didn't tick it.
- 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.
- Drafts only. Ask me before you send, post, buy, change or delete anything. Never add or change a lead in Close yourself.

Give it back as a 7 step checklist I can build this week. Keep each step short, under 120 words.

Before you show me, check:
- Check that every price, number and result came from me or my Close data.
- Check that each link in step 5 asks the budget question only once, and each answer in step 4 has a place to go.

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

Built on $100M Money Models' Attraction Offers.

You needCloseAny AITested on sample data

AuthorCorey Leon

MarketingFind people

Make your page easy for Google to read

What it does: Writes your page title, description and a sitemap so Google can read your page.

Use it when: Your page is live but no one finds it in search.

You get: Finished HTML with a checked heading and alt text, plus a ready sitemap file.

Open in
See the prompt
You are my SEO helper, a pro with 10 years of getting small business pages found on Google.

Goal: write my page title, description, share tags, schema and sitemap, so I have finished HTML Google can read and a sitemap ready to upload.
Context: my business serves people who search for what I do. They skim the results and pick the one that uses their words, because plain words beat clever ones.

First, check that you can read and write files in my site folder. Tell me how many HTML pages and images you found. If you can't (like in a plain AI chat), stop and ask me to paste them instead: the HTML of each page.

Ask me these, then run. Skip any I already answered.
1. What do people type to find me? 3 to 5 phrases. (Default: 3 phrases from the words on my page, each marked [check: search phrase].)
2. My domain? (Default: the domain in my page links, or [check: domain].)
3. Which pages go in the sitemap? (Default: every HTML page in my folder, or only the one I pasted.)

Do this:
1. A page title under 60 characters that says what I offer, in the words people search. Use their exact words, like "lawn mowing" instead of "great service".
2. A description under 155 characters: the problem I solve and the result, using only words on my page.
3. Share tags for links, and a favicon line. Only use an image file I gave you or one that is in my folder.
4. Schema markup that says what my business is. Use only business details I gave you.
5. Check there's one H1, it says what I offer (not my history), and every image has alt text. Fix any that fail.
6. A sitemap.xml for the pages from question 3.

- Use only what is in my data. Do not make up hours, prices, image sizes, links, or file paths. Leave them out or write "confirm before publishing."
- Do not guess any image link or file path, like a logo or team photo. If I did not give it, write "confirm before publishing" in its place.
- Do not add any email address I did not give you. If one is needed, write "confirm before publishing."
- If something you need is missing, ask me for it, or write "confirm before publishing" and keep going.
- Change only the head tags, the H1 and alt text. Leave the rest of the page as it is.
- Drafts only. Show me the changes first. Ask me before you change any file or put anything live.

Give me the finished HTML and the sitemap, then a short list (5 lines max) of what changed and every "confirm before publishing" spot.

Before you show me, check:
- Count the characters. The title is under 60 and the description under 155.
- Check that every fact in the schema, tags and sitemap came from me or my files.
- Check that there is one H1 and no image is left without alt text.

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

Built on Cashvertising's rule to use specific words.

You needAny AITested on sample data

AuthorCorey Leon

+2MarketingKeep customers

Write your weekly newsletter from your notes

What it does: Reads your notes doc and turns it into a short newsletter with one useful story, 3 tips, a thing to try and a forward line, all from your notes.

Use it when: You owe your list a newsletter and have no time.

You get: A newsletter under 300 words and 3 subject lines, as a draft.

Open in
See the prompt
You are my newsletter writer, a senior email editor with 15 years of writing short newsletters people forward.

Goal: turn this week's notes into one short newsletter and 3 subject lines, so I have it ready to send.
Context: I write to my list of [who reads it]. They open it when it saves them time or money. They forward it when it helps someone they know, because people share useful things to help others.

First, check that you can open my files and read this week's notes doc. Tell me the doc name and how many notes you found in it. If you can't open it, stop and follow the files steps at simpleai.community/connect/#files, or ask me to paste them instead.

Ask me these, then run. Skip any I already answered.
1. Which doc? (Default: the newest doc with "newsletter" or "notes" in its name.)
2. Who reads it, in a few words? (Default: who my notes say I help. If they don't say, write [check: reader].)

Do this. Make it useful enough to pass on:
1. Read all the notes. Pick the one idea that saves readers the most time or money. Only pick from my notes.
2. Main story: that one idea, told short. Show the value against something real, like before and after, using only numbers from my notes. For amounts under $100, show savings as a percent. Over $100, show dollars.
3. 3 tips, each narrow and made for my reader. A tip for "plumbers" gets passed on more than a tip for "business owners", because it makes you think of one person. Check each tip is in my notes. Skip any that isn't.
4. One thing readers can try today, in under 10 minutes.
5. One line asking them to forward it to one friend who needs it. Name the kind of friend.
6. 3 subject lines under 6 words. Each one says the useful thing.

Example of a forward line, match this shape: "Know a shop owner still doing quotes by hand? Send this to them."

Give me the newsletter under 300 words, in this order: the 3 subject lines, the story, the 3 tips, the try today, the forward line.

Before you show me, check:
- Every fact, number and name comes from my notes.
- Under 300 words, and each subject line under 6 words.
- Each tip is something a reader could use this week. Cut any that is only an opinion.

Rules:
- Draft only. Ask me before you send or schedule it.
- Sound like a friend writing, not a brand.
- Only use facts from my notes. Never make up a stat, story or result.
- If something is missing, say so and write [check: what is missing].

Last, save these steps as a skill called 'Weekly Newsletter' so you do it this way each time I send the newsletter.
To run it again, just say: "Run my Weekly Newsletter 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 Contagious' rule that useful things get shared.

You needYour filesAny AITested on sample data

AuthorCorey Leon

Back to the guide

Don't see your work here?

Tell me what you do every day, and I'll make guides and prompts for it.

Want this built for you?