Every audience gets exactly the depth they need — no more, no less
A depth profile controls two things per audience: How many levels deep can the generated course go? And how strict is the threshold for actually creating a deeper page? The idea: not every audience needs every detail.
The principle: A depth profile defines not only how deep the course can go, but also how easily it goes deeper. Developers get deeper pages more readily than executives, even when both cover the same topic.
Every potential topic receives a Helpfulness Score from 1 to 10. This score decides whether the topic gets its own page — or just appears as a section on the parent page.
Each dimension is scored individually (1-10), then averaged. A topic with high complexity but low relevance still won't score high. All four factors need to align.
Thresholds per Audience
Lowest threshold — technical topics quickly become dedicated pages
Medium threshold — only genuinely helpful topics get expanded
Highest threshold — only essentials get their own page
A topic has a Helpfulness Score of 7. Which audiences get a dedicated page for it?
The same topic can be treated completely differently for different audiences. Here is a comparison using two concrete examples from a project:
| Topic | 🔧 Developers | 👤 Users | 📊 Executives |
|---|---|---|---|
| Authentication |
✓ HS=9 3 levels of detail |
— HS=6 Overview page only |
— HS=4 Brief mention |
| UI Themes |
— HS=2 Brief mention |
✓ HS=8 Detailed guide |
✓ HS=8 Dedicated page |
| API Rate Limits |
✓ HS=8 2 levels of detail |
✓ HS=7 1 deep-dive page |
— HS=5 Brief mention |
| Licensing Model |
— HS=3 Brief mention |
— HS=5 Brief mention |
✓ HS=9 Dedicated page |
The result: Each audience gets a course that feels tailor-made. Developers dive deep into the technology, users get practical how-to guides, and executives receive a compact overview with strategic focus — all from the same codebase.
The default profiles are a great starting point — but sometimes you need something different. You can explicitly override the defaults when starting, and the skill adapts accordingly.
Documentation: Every override is recorded in the depth map at the end of generation. This ensures full traceability of which depth was chosen and why — whether default or overridden.