BEFORE YOU BUILD · U1NO KEY
Turn a vague idea into a plan
Paste into Chats on lovable.dev or into Plan mode.
I am at a one-day build event in Philadelphia for runners and music people. I have an idea but no plan. Here is the idea in one sentence: [YOUR IDEA]. Help me shape it into something one person can build in four hours with no coding. Answer with: one user, one action, one outcome; the single screen to build first; three features to skip today; and the first prompt I should send to build it. Keep it short.
BEFORE YOU BUILD · U2NO KEY
Pick a look
Send as your second message, or save it under Project settings, Instructions.
Style for this whole app: [pick one]
Race bib: bold, high contrast, oversized numbers, black text on white, one safety-orange accent, tight grid, no gradients.
Liner notes: warm editorial, cream background, near-black text, one deep red accent, serif italics for emphasis, generous spacing.
Night run: dark background, soft off-white text, one neon green accent, rounded cards, subtle glow on active elements.
Apply it everywhere. Use system fonts unless I say otherwise. Keep everything readable on a phone.
BEFORE YOU BUILD · U3NO KEY
Make Lovable ask first
Add this line to the end of any prompt.
Ask me any questions you need in order to fully understand what I want from this feature and how I envision it.
A playlist that matches your pace
Build a one-page web app called PaceTape for runners who want music that matches their stride. The one action: enter a goal pace and get a song list that sits on the right beat.
Screen: a large input for pace per mile (mm:ss) with a slider from 6:00 to 12:00. Below it, three big readouts: pace, estimated cadence in steps per minute, and target BPM. Use this illustrative cadence table and interpolate between rows: 12:00 pace = 156 spm, 10:00 = 160, 9:00 = 167, 8:00 = 172, 7:00 = 178, 6:00 = 184. Target BPM equals cadence. Add a small note: "Illustrative estimate, not training advice."
Below the readouts, a song list filtered to within 3 BPM of the target. Use this sample data for now, stored in the app: 20 songs with title, artist, BPM and genre, spread evenly from 150 to 190 BPM, real-sounding but fictional names. Show a "half time" toggle that also matches songs at exactly half the target BPM.
Style: Race bib. Bold, high contrast, oversized numbers, one orange accent. Mobile first.
Save paces to an account
Add a "Save this pace" button. When clicked, ask the user to sign in, then save the pace and the matched song list to their account so it is there when they come back. Show saved paces in a small list under the slider. Do not change the slider or the readouts.
A share page for each list
Add a shareable page for each saved list at /p/[id] that shows the pace, the BPM and the songs, with a Copy link button. Keep the rest of the app unchanged.
Real songs from Spotify
Needs a Spotify developer client ID and secret.
Replace the sample song list with results from the Spotify Web API search, filtered by tempo from the audio features endpoint. I will add the client ID and secret in the Add secret form, not in chat. Explain what you need from me first.
Audio cues for intervals and splits
Build a mobile-first web app called CueCard that runs an interval workout out loud so the runner never looks at their wrist. The one action: describe a workout in plain English, press start, hear the cues.
Screen 1: a single text box with the placeholder "10 min easy, then 6 x 2 min hard with 1 min easy, then 5 min cool down" and a Start button. Parse that text into timed segments and show the list for confirmation.
Screen 2: a huge countdown for the current segment, the segment name, and the next segment in smaller text. Use text-to-speech to speak each change aloud ("Two minutes hard. Go.") and a 10 second warning before each change. Keep the screen awake while running and keep working if the phone screen is tapped.
Use sample data for the first version. Style: Night run. Dark, one neon green accent, oversized timer.A spoken pep talk
Add a short spoken pep talk at the halfway point of each hard interval, generated by the AI model from the workout name and the segment number. Keep it under 8 words. Do not change the timer logic.
Save workouts
Add a Save workout button that stores the parsed workout in the user's account after sign in, and a list of saved workouts on screen 1.
A route map with a playlist per loop
Build a web app called LoopNotes for a run club that runs the same loops every week and wants a soundtrack for each one. The one action: pick a loop, see the map, hear what the group runs to.
Home: a list of three loops with sample data: "Kelly Drive out and back, 4.0 mi", "Schuylkill Banks, 3.1 mi", "Art Museum steps loop, 2.0 mi". Each card shows distance, a one-line description, and a playlist of 8 fictional songs with artist and BPM.
Loop page: an interactive Google Map centered on the loop's start point with a drawn route line using sample coordinates in Philadelphia, the distance, and the playlist. Use Lovable's managed Google Maps connection.
Style: Liner notes. Warm editorial, cream background, one deep red accent.
Let members add songs
Let signed-in users add a song to any loop's playlist with a title and artist field. Save it to the database and show who added it. Do not touch the map.
Tonight's loop banner
Add a "Tonight's loop" banner at the top of the home page that a host can switch between loops after signing in.
Generate your finish-line song
Music generation uses credits per finished track.
Build a one-page app called Finish Line that generates a short personal anthem for the moment a runner crosses the line. The one action: fill in three fields, press Generate, play the song.
Fields: your name, your race and goal time (for example "Philadelphia Marathon, 3:45"), and a mood picker with four options: triumphant, emotional, gritty, playful. A Generate button.
On Generate, use the Lyria 3 Clip Preview music model to create an instrumental clip of about 30 seconds that matches the mood, with a genre that fits (triumphant = brass and drums, emotional = piano and strings, gritty = guitar and heavy drums, playful = synth pop). Show a waiting message that says "Writing your finish line song, about a minute" while it generates, then an audio player with a download button. Save each finished track to the app's storage so the user can replay it later from a "My songs" list.
Style: Race bib. Big type, high contrast, confetti only on the finished state.
Sing my lyrics
Add an optional lyrics field, up to 40 words. When it is filled, generate the clip with vocals singing those lyrics instead of an instrumental. Keep the instrumental path as the default.
A share page per song
Add a share page at /song/[id] with the runner's name, race, mood and the player, plus a Copy link button.
A run-club RSVP page with a song pick
Build a one-page RSVP site called Saturday Crew for a free weekly run. The one action: claim a spot in under 20 seconds.
Top: the run name, "Saturday 8:00 AM, Art Museum steps", a short line "Walkers, joggers and runners. Nobody runs alone." and a live counter "14 of 30 spots left."
Form: name, email, one optional field "one song for the week's playlist", a checkbox "I am new to the group", and a Claim my spot button. Save every RSVP to the database. Cap the room at 30. When 30 is reached, change the button to "Join the waitlist" and keep collecting names in a waitlist table. After submitting, show a confirmation state with the song they picked and a Copy invite link button.
Bottom: a "This week's playlist" list that shows the songs people picked, first names only, newest first.
Style: Liner notes. Warm editorial, cream background, one deep red accent, serif italic for the tagline.
A host-only list
Add a host-only page at /host behind sign in that lists every RSVP with name, email, song, new-member flag and time, with a Download CSV button. Only the host can see it. Do not change the public page.
Confirmation emails
Needs a Resend account.
Send a confirmation email when someone claims a spot, with the run time, the location and their song. Tell me what you need from me to connect Resend.
Liner notes for the marathon mixtape
Build a web app called Side B that writes liner notes for a running mixtape. The one action: paste a tracklist, get liner notes you would print on the sleeve.
Screen: a big text area for a tracklist, one song per line as "Artist, Title", with 12 sample songs prefilled (fictional names). A dropdown for the occasion: "marathon weekend", "first 5K", "long run Sunday", "race morning". A Write the notes button.
On click, use the AI model to write 150 to 200 words of liner notes in the voice of a 1990s cassette insert: warm, specific, a little funny, no hashtags. Then show the notes next to a printable sleeve preview: a square "cover" with the mixtape title, and the tracklist on the back with the notes. Add a Print button and a Copy notes button.
Style: Liner notes. Cream paper, near-black type, one deep red accent, serif italics for the notes.
A QR code on the sleeve
Add a QR code to the sleeve preview that points to a public page at /tape/[id] showing the same tracklist and notes. Save each tape to the database when the notes are generated.
Order the burned CD
Needs a Shopify store.
Add a "Order the burned CD" button on the public tape page that links to a Shopify product. Explain what you need from me to connect the store.
A producer's split sheet
Build a web app called Split Sheet for producers and artists who finish a track together and need to agree on who owns what before anyone forgets. The one action: create a split sheet everyone can sign off on.
New sheet form: song title, date, and a contributors table with name, role (writer, producer, performer, mixer), email, and percentage. Show the running total and warn in red when it is not exactly 100 percent. A Save sheet button that requires sign in.
Sheet page: a clean one-page view of the sheet, a Download PDF button that produces a printable PDF with the song title, date, the table and a signature line for each contributor, and a Copy link button so collaborators can see it.
Use sample data for the first version. Style: Race bib. Bold, monochrome, one accent, dense but clear table.
Approvals
Let each contributor, after sign in with the email on the sheet, press an Approve button next to their name. Show a green check and the time of approval. Lock the percentages once everyone has approved. Do not change the PDF layout.
A one-page drop for your release or race
Build a one-page drop site for [a release or a race], named "[YOUR DROP NAME]". The one action: leave your email to be first in line.
Sections top to bottom: a full-width hero with the drop name, the date "[DATE]" and a live countdown; a 3 line description; a cover image placeholder; an email field with a "Put me first" button that saves the email to the database and shows "You are number [n] in line"; and a footer with your name and city.
Use real-sounding copy, not placeholder text. Style: Night run. Dark, one neon accent, oversized countdown.
A private list
Add a private /list page behind sign in that shows the emails, the position and the time, with a Download CSV button. Do not change the public page.
Pre-orders with Stripe
Needs your own Stripe account. Free plan can connect one.
Add a "Pre-order for $12" button using my own Stripe account in test mode. Tell me what you need from me and use the 4242 test card to verify the flow in preview.
WHEN IT BREAKS · F1NO KEY
Describe what broke
First press Try to fix once or twice. Then send this.
Something is broken. Where: [page or button]. What I expected: [x]. What happened instead: [y]. Here is the exact error text: [paste]. Fix only this and leave everything else as it is.
WHEN IT BREAKS · F2NO KEY
Find the root cause
Switch to Plan mode for this one.
Investigate why [the problem] keeps coming back and find the root cause before changing any code. Explain it in plain English, then propose the smallest fix.
WHEN IT BREAKS · F3NO KEY
Go back to the last working version
Not a prompt. Open version history, pick the last version that worked, restore it. Or edit an earlier message and choose Revert and resend.
Restore the last version where [feature] worked, then tell me what changed between that version and now.
Mobile check
Check the whole app in mobile view. Fix anything that overflows, overlaps or is too small to tap. Do not change the design otherwise.
Security check
Review the security of this app and fix any critical issues before I publish.
An about page for the judges
Add a small /about page that says what this app does in three sentences, who it is for, and "Built at Shake & Ship, Philadelphia Marathon weekend, November 2026 by [NAME]". Link it from the footer.
Then press Publish, copy the lovable.app link, record 60 seconds of screen, and submit both.