How it works
A pipeline, not a prompt
Specialised agents plan the course, design and build each slide, and check the result in a real browser. Every stage is saved as it finishes, so a build survives being interrupted — and so does the work already done.
What happens after you press Build
These are the real stages, in the order they run. You watch them tick past in the workspace.
01Reading the brief
One agent settles what the course is actually about before anything is structured — key facts, the terms it will use, and the assumptions it is working from. This is the only stage allowed to look things up in the world, so those facts are established once rather than re-derived in every slide.
02Designing the outline
Modules, then lessons, then the objective each one is there to meet. Objectives are written with the verbs your chosen Bloom level licenses, so a course set to Apply cannot quietly settle for a list of definitions.
03Your approval, if you asked for it
Review Outline First pauses the build here and hands you the plan. Edit it, or type the change you want and get a rewritten plan back. Approving it is what starts the work. Skip the option and the build runs straight through.
04Planning the slides
The approved outline becomes a deck: what each slide teaches, whether the learner reads, does something, plays or is assessed, which pictures it needs, and the course’s own colours, fonts and art direction. Assessment follows the question count, types and pass mark you set.
05Making the pictures
Photographs and illustrations are generated for the slides that asked for them, before those slides are built, so each one is designed around the picture it actually has rather than a gap where a picture might go.
06Designing and building each slide
Every slide is designed and coded on its own, as its own document, with no template and no component library. The opening slide is built first and shown to the others as a style reference, which is what makes thirty independently written slides read as one course.
07Packaging
The slides are assembled into the course frame — navigation, progress, resume and every call your LMS hears. That frame is ours and identical in every course, so the reporting cannot be forgotten or malformed however the slides were designed.
08Testing every slide in a browser
Each slide is opened inside the real frame with a simulated LMS behind it: does it load, does anything throw, does the text fit, and — where a slide gates or scores — can it actually be completed and does the score reach the LMS. Slides that fail go back to be rebuilt with the findings.
09Reviewing how it looks
Screenshots of every slide go to a reviewer that judges what a learner would see: clipped text, unreadable contrast, a broken layout. Anything flagged gets one repair round, and a fix that breaks a working slide is reverted.
Then keep changing it
A finished course is not a finished conversation.
Ask for a change in the chat — rewrite the summary, make the quiz harder, add a slide after the case study, change the course’s colours — and only what you asked about is rebuilt. The other slides are left exactly as they were.
Every change is checked before it counts: the edited slide is loaded in a browser again, and if it no longer runs cleanly the previous version is put back rather than left live.
You can publish a version, share a link so people can take the course with no LMS and no sign-in, and see how far they got. Or duplicate the whole thing and take the copy in a different direction for a different audience.
Build your first course
Describe what it should cover. Watch it get designed. Download a package that imports.
Start building