# Quick refresher

A short yearly refresh: questions first, so people who know move on.

A course of this type has `"courseType": "quick-refresher"` in `kapi-works.json`.

## Its shape

Keep the whole refresher to 8 to 12 minutes. Every page starts with its question, and the feedback on each choice and the explanation do the teaching in one or two sentences. Keep any text after the question short.

## What Kapi checks

Kapi runs [every check](https://docs.kapiworks.com/build/reference/checks) on every course. These run only on this type:

| Check | Severity | What Kapi says |
| --- | --- | --- |
| [`refresher_question_first`](https://docs.kapiworks.com/build/reference/checks/refresher-question-first) | Error | This page doesn't start with its question. In a quick refresher, every page asks first and the feedback teaches. |
| [`refresher_too_long`](https://docs.kapiworks.com/build/reference/checks/refresher-too-long) | Warning | This refresher takes about … minutes. A quick refresher takes 8 to 12. |

## The prompt

Copy it into your own AI and attach the example. It stays under 2,000 characters, so it fits the smallest chat box.

```text
Kapi Works course prompt · Quick refresher · package 2

Make a quick refresher for Kapi Works, my company's learning platform. Answer with one JSON object in one code block: { "schema": "kapi.works.bundle/1", "files": { … } }, with "courseType": "quick-refresher" in kapi-works.json. Kapi checks it and fixes small problems itself.

THIS TYPE
Keep the whole refresher to 8 to 12 minutes. Every page starts with its question, and the feedback on each choice and the explanation do the teaching in one or two sentences. Keep any text after the question short.

RULES
1. Copy the layout of Kapi's attached example: its files, fields and ID style. Replace all its content; never copy its topic or its words.
2. Every word a learner sees goes in "words/en-GB.json" under an ID. Everywhere else names the ID.
3. Right answers go in questions.json. Every choice has feedback saying why it is right or wrong, and every question has an explanation.
4. Test pool questions go in "assessments" in kapi-works.json and sit on no page.
5. Never draw a test, score, certificate, signature or "I agree". Kapi adds its own after the course.
6. No personal data: write {company.name}, and a contact block for who to ask, never a real name, email or phone.
7. Use only my documents for rules and figures. If they don't say, ask me.
8. Give the whole object. Never shorten it or write "…".

If you can open web pages, read https://docs.kapiworks.com/build/llms-full.txt first.
Ask me up to five questions, then propose an outline (lessons, minutes, questions) and wait for my OK.
If Kapi's example isn't attached, ask me for it.
```

## The example

[`quick-refresher.json`](https://docs.kapiworks.com/build/examples/quick-refresher.json) is a whole course of this type for a made-up company, as one `kapi.works.bundle/1` bundle of its data files. Your AI copies its layout, not its words.
