Rafy is Keypra's slide co-author. Slides are stored as structured data in the database and rendered with synced Framer Motion animations — so they look the same in authoring, in preview, and in a live session.
You describe what each slide is for; Rafy proposes the layout, copy and animation. You stay in editorial control — accept, edit or reject each slide.
Build a deck
Start from intent, not a blank slide
Tell Rafy who the audience is and what they should be able to do after the session. The first draft of the deck is shaped by that.
Iterate slide by slide
Each slide is an editable block: title, body, optional visual, animation profile. Edit the copy directly or ask Rafy to revise.
Drop in your own examples
Real prompts and outputs from your team beat any generic template. Use the example block to anchor each concept.
Preview the animations
Hit Preview to see exactly what learners will see. Adjust pace if needed — slow is usually better than flashy.
Lock the deck
When ready, lock it. Locked decks won't change mid-session if you keep iterating in the background.
What you can put on a slide
Concept block
Title + 1–3 bullets. The workhorse for explanation.
Prompt block
A real prompt rendered with the same colour-coded blocks learners use in the Composer.
Before/after
A weak prompt next to a strong one. The single highest-impact teaching block.
Activity prompt
A task learners do live in the Lab. The slide pauses; their results flow back to your console.
Rafy won't impersonate experts, generate fake quotes, or fabricate citations. If you want an expert's view in your deck, paraphrase it and credit them.