← ClaudeAtlas

learning-tracklisted

Create a multi-audience learning track, course, or study companion teaching the concepts behind a software project using the project itself as the example. Produces modular, beginner-first Markdown lessons, repo-first, taking a reader from zero to understanding how it works and why. Use this whenever the user wants a learning track, course, curriculum, study guide, tutorial series, teaching material, lesson modules, or to turn a codebase into educational content. Use it even for requests like "help people learn how my project works" or "make study material from this codebase". Teaches concepts and the reasons behind them for newcomers (a tutorial, in Diataxis terms) — NOT step-by-step task instructions (use usage-guide), NOT a look-up reference (use project-faq), NOT contributor onboarding (use onboarding-companion), and NOT a deep design-and-decisions doc for engineers who already use it (use architecture-and-decisions).
imrohitagrawal/project-doc-skills · ★ 0 · AI & Automation · score 58
Install: claude install-skill imrohitagrawal/project-doc-skills
# Learning Track Builder Version: 1.4.0 · see `CHANGELOG.md`. Build a **learning companion**: a set of modular lessons that use a real software project as the worked example to take readers from "curious but lost" to "I understand what this system does, why it is built this way, and how I would start building something like it." This skill owns the *workflow and the page template*. The shared writing standard lives in `references/house-style.md` — **read it first, every time.** The project's facts, audience targets, palette, and licence live in the project profile (`references/house-style.md` Section 1 explains how to find or create it). **Diátaxis mode:** primarily *tutorial* (learning-oriented) with *explanation* layers. Keep it distinct from a how-to usage guide and a reference FAQ. --- ## Before you start: what this needs, when to run it, where it fits This section answers three questions a new project raises: *do I have what the skill needs yet, at what point in the build do I run it, and how does it sit next to the other documentation skills?* Read it before the workflow. ### What this skill needs (the inputs) The learning track teaches the *concepts the project actually exercises*, so it has to read the project first. Before writing modules, make sure these exist and point the skill at them: - **The filled project profile** (`docs/project-profile.md`) — owner, brand, licence, palette, audience targets, the public-vs-internal setting, and the canonical worke