GRYT Club crestgryt
Claim a spot

GRYT CLUB / SHAKE & SHIP / BUILD KIT

The build kit.

Everything you need to make one small thing on Friday.

B1 · What a hackathon is

A hackathon is a room where everyone makes one small thing.

What it actually is

A hackathon is a few hours where a room of people each make one small thing, then show it. That is the whole idea. At Shake & Ship the thing is a simple web app about music or running, the room is in Philadelphia, the tool is Lovable, and the clock runs from noon Friday to 11:59 PM ET Tuesday, November 24. You describe what you want in plain English. Lovable writes the code. You change it by typing. You publish it to a link. You send us the link. Nobody will ask you to code.

How the day works

Noon to six, you sit with other runners and producers and build. If you get stuck, the person next to you or a host helps. By Tuesday night, November 24, you send two things: a live link and a short showcase, which is a 60 second screen recording or three screenshots and a paragraph.

What ship means here

Ship means your project is live at a public link. A half-finished idea that is live beats a perfect idea on your laptop. Lovable publishes to a free lovable.app address with one click.

01

Describe

Type what you want in plain English

02

Change

Say what to adjust, one thing at a time

03

Publish

One click, free lovable.app link

04

Submit

Send the link and a 60 second showcase

B2 · Lovable in a minute

Watch it work before you touch it.

Lovable Explain In 1min, from the Lovable team, published November 4, 2026.

Lovable turns a plain-English description into a working web app. The screens, the database, sign-in and hosting are included. Lovable Cloud is the built-in backend. Lovable AI adds text, voice, music and image models with no API keys. You own the code.

DATABASESIGN-INVOICEMUSICMAPSPUBLISHNO CODE
Two more minutes on Cloud and AI
B3 · Prompts you can paste

Prompts you can paste.

Every prompt below builds something real in one send, with sample data and no API keys. Copy it, or press Open in Lovable and it will be typed in for you. Then change one thing at a time.

BEFORE YOU BUILD · U1
NO 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 · U2
NO 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 · U3
NO 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.
P1 · STARTER
NO KEY

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.
P1 · LEVEL UP
CLOUD

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.
P1 · LEVEL UP
CLOUD

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.
P1 · STRETCH
STRETCH

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.
P2 · STARTER
NO KEYAI

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.
P2 · LEVEL UP
AI

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.
P2 · LEVEL UP
CLOUD

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.
P3 · STARTER
NO KEYMAPS

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.
P3 · LEVEL UP
CLOUD

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.
P3 · LEVEL UP
CLOUD

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.
P4 · STARTER
NO KEYAI

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.
P4 · LEVEL UP
AI

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.
P4 · LEVEL UP
CLOUD

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.
P5 · STARTER
NO KEYCLOUD

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.
P5 · LEVEL UP
CLOUD

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.
P5 · STRETCH
STRETCH

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.
P6 · STARTER
NO KEYAI

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.
P6 · LEVEL UP
CLOUD

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.
P6 · STRETCH
STRETCH

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.
P7 · STARTER
NO KEYCLOUD

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.
P7 · LEVEL UP
CLOUD

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.
P8 · STARTER
NO KEYCLOUD

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.
P8 · LEVEL UP
CLOUD

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.
P8 · STRETCH
STRETCH

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 · F1
NO 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 · F2
NO 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 · F3
NO 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.
SHIP IT · S1
NO KEY

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.
SHIP IT · S2
NO KEY

Security check

Review the security of this app and fix any critical issues before I publish.
SHIP IT · S3
NO KEY

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.

B4 · One build, start to finish

One build, start to finish.

PaceTape, the pace-to-playlist idea from the presets, built in six prompts. About 45 minutes for a first-timer. No API keys.

  1. 01

    Describe it

    You type
    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.
    You see3 to 5 min

    A working page: pace slider, three readouts, a song list that changes as the slider moves.

  2. 02

    Change it by chatting

    You type
    Make the BPM window adjustable with a 1 to 5 BPM stepper next to the list. Keep everything else the same.
    You see2 min

    The same page with a stepper. The list tightens and loosens.

  3. 03

    Make it yours

    You type
    Rename the app to PaceTape. Switch the accent to safety orange. Make the readouts twice as big on phones.
    You see2 min

    Same structure, your look. Or click an element with the preview toolbar and describe the change.

  4. 04

    Make it remember

    You type
    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.
    You see5 to 8 min

    A sign-in screen and a saved list. Lovable turns on the database and accounts by itself.

  5. 05

    Make it shareable

    You type
    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.
    You see5 min

    A public page per saved list. This is the link judges will click.

  6. 06

    Ship it

    You type
    Check mobile view and fix anything broken. Then I will publish.
    You see5 min

    Press Publish. Copy the lovable.app link into the submission form.

WATCH THE SAME SIX PROMPTS

Until our own recording is up: the official 24 minute walkthrough. Chapters: first prompt 0:27, Lovable Cloud 5:57, Lovable AI 11:17, publishing 21:45.

B5 · THE DESK

The music x running desk.

Open the tab for the job. Each card is one thing you can use today.

Pace to BPM

At a 9:00 pace the illustrative table uses about 167 steps per minute, and target BPM equals cadence. It is an estimate for a playlist, not training advice.

Listening map

The mixtape page lays a cut on the Philadelphia course. Course shape from a 2026 guide using USGS elevation, not the race organizer. Listening map only. Not a pace plan.

Sample songs first

The prompts use fictional names on purpose. Spotify search needs your own developer keys. Do not ship someone else's recording unless you have a right to use it.

Split sheet

A page that says who contributed and whether the percentages add to 100.

B6 · ASK

Ask.

The short answer is the first sentence.

Do I need to know how to code?

No. You describe what you want in plain English. Lovable writes the code.

Do I need a race bib?

No. No pace requirement and no race registration. The shakeout is a 30-minute walk or run, and it is optional.

What do I bring?

A laptop if you want to build. A phone is enough for the shakeout. The room is 2212 Spruce Street, Philadelphia.

When do the Lovable credits arrive?

By email before Friday, if you are registered. This page does not publish a credit count.

Can I come for only the run, or only the build?

Yes. Both is best. Noon to 6 PM.

Shake & Ship is an independent event during Philadelphia Marathon weekend. It is not an official Philadelphia Marathon event. The cadence numbers are illustrative, not training advice. The listening map is not a pace plan. Lovable credits are emailed to registered participants before Friday. Pop Site Pro plans are offered and terms are pending. You keep what you make. A confirmation email is your ticket. 100 spots.