Recipes
A recipe is the shortest path from something you already have to a course your LMS can import. Each one is a single copy-paste prompt plus a single attachment — no terminal, no JSON, no file paths. You paste the prompt into your AI assistant (with OELTKit connected), attach the file, and let the conversation do the rest: it scaffolds the course, fixes its own validation findings, and hands you a .oeltcourse file (and, when you ask, the LMS package).
How a recipe runs
Section titled “How a recipe runs”The conversation is the interface. You don’t pick “SCORM 1.2 or 2004?” — you say which LMS you use (or nothing, and get a safe default). Validation findings come back as plain-language fix offers, not error codes. Mastery thresholds, cmi5, and theming exist when you ask for them, never in the default flow.
Under the hood every recipe walks the same path:
- Start — scaffold a course with sensible defaults (targets SCORM 1.2 + web, default theme, sensible tracking).
- Build — turn your source material into pages and interactions.
- Check — validate; the assistant repairs anything the validator flags.
- Ship — export a
.oeltcoursefile you keep, and package a.zipfor your LMS when you’re ready.
The launch set
Section titled “The launch set”- Course from a PowerPoint — the #1 real-world entry point.
- Storyboard to SCORM — a Word or PDF storyboard becomes a course.
- Design prototype to course — a Claude/HTML prototype, made trackable.
- Update an existing course — attach a
.oeltcourseand revise it. - Translate my course — attach a
.oeltcourseand localize it. - Quiz from a policy document — turn a policy into a scored check.