The two mandatory setup decisions that shape every course — before a single line of HTML is generated
The skill doesn't create one course for everyone. It creates a separate course per audience. Each group asks different questions about the code — and gets exactly the answers it needs. Depth, tone, and focus differ fundamentally.
🏷️ Custom audience: None of the three fit? Define your own audience. Describe who the readers are and what they want to know — the skill creates a tailored course with appropriate depth and language. Example: "QA engineers who want to understand the testing system".
You can select multiple audiences at once. The skill then generates a separate set of HTML files for each group — in the same output folder, but with different file names.
The naming rule is simple: the first (most general) audience gets index_en.html, all others get a suffix. The priority order is: Users > Executives > Developers > Custom.
Why separate files? Each audience has its own curriculum, its own helpfulness scores, and its own navigation tree. Mixing them would dilute the focus — so the skill generates three lean courses rather than one bloated one.
The second mandatory question: How will the files be used? The answer determines whether the skill builds header, footer, and external links into the HTML files — or delivers them as self-contained standalone files.
| Property | Standalone | Embedded |
|---|---|---|
| Use case | Sharing via email, Slack, download | Part of a website or documentation |
| Header links | None | GitHub repo, docs link |
| Footer | None | Legal notice, privacy policy, copyright |
| External links | No external references | Open in new tab (target="_blank") |
| Works offline | Yes — fully self-contained | Yes, but links require network |
| Additional info needed | None | GitHub URL, legal notice URL (required) |
Which mode should you choose if you want to share the course via Slack?
If you choose embedded mode, the skill asks for a few additional pieces of information. Two are required, two are optional — but all of them improve the result.
You don't need to choose a language — every course is automatically generated in both German and English. Always. No exceptions. There is no "German only" or "English only" option.
How the linking works: Every file contains a flag icon in the navigation that links to its language counterpart. The naming follows a fixed pattern:
Why always bilingual? Software teams are international. A course that exists in only one language always excludes someone. That's why bilingual output isn't an option — it's the default.