Your first prototype

Make the prototype fit your actual Tuesday, and see how it works.

1. 1

   Choose your path

   In-app

   Your first real product decision: apply your style & logo now, or keep sharpening how it works first. Both are right.

   Do: Pick: style first, or function first

2. 2

   Vibe coding was made for clinicians

   In-app

   Why most healthcare software misses — and how AI turns the people who know the work into the people who build the tools. Plus the three parts of what you just watched.

   Do: Name the three parts of what you watched

3. 3

   Your world, in data

   In-app

   The context interview: your role, your team, your typical patients, the systems you touch daily. Then watch your prototype regenerate with your world's data.

   Do: Build your clinical context profile

4. 4

   The synthetic-data rule

   In-app

   Why we never prototype with real patient data, and how realistic synthetic data makes your prototype credible AND safe.

   Do: Spot the PHI: a 60-second drill

The prompting skill, learned by doing reps on your own prototype.

1. 1

   Anatomy of a prompt

   In-app

   The pattern behind every good build instruction — context, intent, constraint — shown on a real prompt with the skeleton labeled.

   Do: Label the anatomy of a real prompt

2. 2

   Edit this prompt

   In-app

   Kit drafts a prompt for YOUR prototype with the best practices called out. Load it into the chat, make it yours, run it — a real change, from a prompt you shaped.

   Do: Edit Kit's draft prompt, then run it

3. 3

   Talk, don't type

   In-app

   Typing trims ideas before they're fully out. Dictation lets you think out loud — and speech-to-text is good enough now that you barely clean it up.

   Do: Dictate one change request with the mic

4. 4

   Close the loop

   In-app

   AI moves fast and confidently, even when it has misunderstood you. Make it mirror back its understanding before it builds — catch the miss while it's cheap.

   Do: Ask Kit: 'tell me what you understood first'

5. 5

   The iteration loop

   In-app

   Assess, adjust, repeat — the loop clinicians already know from titrating anything. Three more self-authored reps on your prototype.

   Do: Three reps: three changes you chose

Pictures beat paragraphs — your visual channel to the build.

1. 1

   A picture's worth 1,000 prompts

   In-app

   Drop a screenshot — your EHR, a site you like, the confusing thing itself. The image carries exactly what your words would struggle to.

   Do: Drop one screenshot and use it in a change

2. 2

   The napkin sketch

   In-app

   Some layouts are faster to draw than to describe. Boxes, arrows, labels — photograph it with your phone and drop it in; the AI reads through bad lighting and crooked angles.

   Do: Sketch a screen, photo it, drop it in

3. 3

   Bug reports that work

   In-app

   "It's not working" leaves the AI guessing. Steps to reproduce, expected, actual — the three-part structure engineers use — turns a complaint into a precise fix.

   Do: File one real fix as a three-part report

From plausible demo to the thing you'd actually show your team.

1. 1

   Your use case, in writing

   In-app

   What a use case actually is, why product teams write one before they polish anything — and then you detail yours with Kit: who opens this, when, what they must see, what happens next.

   Do: Detail your use case with Kit

2. 2

   The use case, sharpened

   In-app

   Who opens this on a Tuesday, and what do they need in the first ten seconds? Tighten the prototype around the real moment of use.

   Do: The Tuesday-morning test

3. 3

   Content that rings true

   In-app

   Replace generated sample data with synthetic content shaped by YOUR context profile — the layer that makes colleagues nod instead of squint.

   Do: Rebuild the data to match your world

4. 4

   Match the brand

   In-app

   Point at a website and inherit its fonts, colors, and style — then refine with exact hex values. Inherit the brand; don't clone the site.

   Do: Inherit a real brand, then tune it

5. 5

   Show one colleague

   Reflect

   Send the share link to one person who lives the problem. Their first reaction is your first user research.

   Do: What did they say? Capture it.

What you built, what you keep, and three roads from here.

1. 1

   Your build story

   In-app

   The record of what you made and the practices you used — plus the option to publish it to the gallery with your role on it.

   Do: Publish to the gallery (or keep it private)

2. 2

   Your Vibe Skills, to keep

   In-app

   The full skill library as a downloadable PDF — every practice you used badged, the ones you haven't tried yet queued. Yours regardless of what you do next.

   Do: Download your skills PDF

3. 3

   Three roads from here

   In-app

   Keep sharing the link (included). Own it fully — move it to GitHub and your own Vercel, with Kit helping inside Claude Code. Or let us host it — the collaboration microsite with Kit's memo, colleague comments, and continued Kit time.

   Do: Pick your road