Where Let’s Vibe ideas take shape

Before we start, make sure you're working from the latest version of the vibe-prototypes repo on GitHub (the main branch). Read AGENTS.md and follow it for everything we do. Tell me in plain language if anything is in the way, and give me a one-paragraph summary of what's changed recently so I know what my teammates have been up to.

I'd like to create a brand-new Let's Vibe prototype.

What it is: [describe it in plain words, e.g. a flow where a Seeker books a place at an event]
Who it's for: [Seeker, Practitioner, or both]
Screens or steps I imagine: [list them, or write "you decide"]
Name: [a short name like event-booking, or write "pick one"]

Read AGENTS.md first and follow it exactly. Build it as v1 in the right folder, using our brand. Check it on a phone and a computer, in light and dark mode and with the keyboard only, and make sure every screen has its own link that still works after a reload and with the Back button. Once it passes, save it straight to main and publish it (no pull request needed), updating from main first so you never overwrite a teammate's work. When you're done, tell me in plain language what you built, give me the live link and how to open it locally, and anything you could not check.

Create a new version of the prototype [name, e.g. wellness-hub]. Start from its latest version and leave all older versions untouched.

What I want to change: [describe the changes in plain words]

Read AGENTS.md first and follow it. Write a changelog that explains what is different from the previous version, update the version list, and run the same checks (phone and computer, light and dark, keyboard, working links and Back button). Once it passes, save it straight to main and publish it (no pull request needed), updating from main first. Tell me in plain language what changed and give me the live link to the new version.

Make a small change to the latest version of [prototype name]: [describe the change].

Only do this in place if it's a minor fix that doesn't change what people already reviewed. If it changes the design, flow or behaviour, stop and ask me, and make a new version instead. Record the change in that version's changelog, check it still works on a phone and a computer, then update from main, save it straight to main and publish it (no pull request needed). Give me the live link.

Build a Let's Vibe prototype from this design: [paste a Figma link, or attach screenshots or a sketch].

Purpose: [what it should show or prove]
Name: [a short name, or write "pick one"]

Read AGENTS.md first. Match our brand tokens (colours, fonts, spacing) rather than copying exact values from the design, and tell me where you made a judgement call. Check phone and computer, light and dark, keyboard, and working links. Once it passes, update from main, save it straight to main and publish it (no pull request needed), and give me the live link.

Check [prototype name and version, e.g. partners v1] against our standards in AGENTS.md: accessibility, phone and computer layouts, and links and the Back button. List anything that fails in plain language, fix it, and check again. Tell me exactly what you tested and what you could not.

Save and publish my work. First update from the latest main so nothing a teammate did gets overwritten. Run the checks in AGENTS.md (the app builds, my prototype loads, phone and computer layouts, working links). If those pass, commit with a clear message, push straight to main (no pull request needed), and tell me when it's live along with the link and a two-line summary I can paste to the team. If something conflicts with a teammate's work, stop and explain it simply before changing anything.

I'm new to this repo and not technical. Explain in plain language what's here, how prototypes are organised, how I can preview them, and what I'd do to start my first one. Keep it short and ask me what I want to make.