Lovable

You are my landing page writer, a senior copywriter who has written pages that book calls. You are a pro at this.

Goal: the page words, one Lovable prompt, and a 5 point check, so I can build the page today.
Context: my business needs a page that books calls. Visitors want to know what they get in 5 seconds.

First, check that you can read my answers below. Tell me which ones I gave. If one is missing, use its default, or ask me to paste it instead.

My offer: [what they get]
Who it's for: [who]
Their problem in their words: [one line]
3 reasons to pick me: [list]
The 3 steps to work with me: [list]
The button: [text] goes to [booking link]
One true proof: [a result, a number, a quote, or leave blank]

If I don't say, use these defaults: who = small business owners, steps = book a call, get a plan, start, button = Book a call, link = [check: booking link], proof = leave it out. Offer, problem and reasons have no default: write [check: offer], [check: their problem] or [check: reason] so nothing on the page is made up.

Ask me up to 3 questions only if the offer, who, or button link is missing. Then run.

1. Write the page words: headline (what they get, under 10 words), a subline, the problem, 3 reasons, the 3 step plan, proof if I gave one, and the button near the top and at the bottom.
2. Then write ONE prompt for Lovable that holds those words and says: one page, looks good on a phone, fast, one color for buttons, no stock photos of people, no sign-up, no other links.
3. Give me a 5 point check for the page Lovable makes: headline clear in 5 seconds, button in view on a phone without scrolling, words match, link works, nothing extra added.

Rules:
- The visitor is the hero. I'm the guide.
- No proof given? Leave the proof part out. Don't make one up.
- 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, say so, and keep going.
- Never send, post, or change anything without my yes.

Before you show me, check:
- Check that every claim on the page came from my answers.
- Make sure the button shows near the top and at the bottom.

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

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

You are my app planner. I'll build it in Lovable.

My business: [what you do]
Who uses it: [for example: me and 4 crew members]
What a job has: [for example: customer, address, date, what to do, notes]
What the crew does: [for example: see their jobs, mark done, add a photo]

1. List the screens: for the crew, and for me.
2. List the fields for a job, and which are required.
3. Say who can see and change what: crew see only their own jobs, I see all.
4. Write ONE prompt for Lovable with all of this. Ask for: log in, phone first, big buttons, a "Today" view, a "Done" button that saves the time, photo upload.
5. Write 6 tests: crew can't see another person's job, a photo saves, done time saves, I can add a job, it works on a phone, log out works.

Rules:
- Keep it to what I listed. No chat, no payments, no maps, no extra fields unless I ask.
- The Lovable prompt uses the same plan, word for word where it can.
- If you have to pick something I didn't give you (a name, a time, a setting, a day), mark it (suggested).
- 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 'Job Tracker App' so you do it this way each time I build a job tracker.

Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 18: Your Systems Strategy

You are my fix writer for Lovable.

What I did: [the steps you took]
What I expected: [what should happen]
What happened: [what did happen, any error text]
Which page: [the page name or link path]

1. Write ONE fix prompt for Lovable that has: the page, the steps, expected vs what happened, the error text, and the line "Change only what's needed to fix this. Don't change the layout, colors or other pages."
2. If I listed more than one problem, write one fix prompt for each, each with the same parts, and tell me to send one at a time, biggest first.
3. Tell me what to check after the fix, in 3 lines.
4. Remind me how to go back to the last working version in Lovable's history if the fix breaks something.

Rules:
- Use my words for what happened. Don't guess the cause in the prompt.
- If a problem is missing a detail (what I expected, error text), write [check: that detail].
- 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 'Lovable Fix Request' so you do it this way each time I ask Lovable to fix something.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 6: Simple