REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A Claude Code skill that turns any codebase into a beautiful, interactive single-page HTML course for non-technical vibe coders.
Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/skills/zarazhangrui-codebase-to-course)MCP-Server, die die KI für dieselbe Arbeit mit Diensten verbinden
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
Gleiche Art Arbeit, sortiert wie die Skill-Liste
| Dieser codebase-to-course | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Anbieter | zarazhangrui | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub-Sterne | 5.810 | 463.670 | 233.682 | 148.887 | 143.987 |
| Letzte Codeänderung | 31. März 2026 | 17. Nov. 2026 | 20. Apr. 2026 | 17. Nov. 2026 | 16. Nov. 2026 |
| Lizenz | – | MIT | – | Apache-2.0 | MIT |
1 Skills (Anweisungssammlungen) von zarazhangrui, die eine KI liest und befolgt · kein MCP-Server
MCP = die Hände
Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.
Skill = das Handbuch
Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.
Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.
Claude Code
Laut README des Anbieters und den Ordnern im Repo
GitHub account zarazhangrui (person), 2 years old
★ 5.810 stars · code last changed 31. März 2026
2 scripts that can run on a computer: references/build.sh, references/main.js
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit ff8837e (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
Zuerst: Welche KI nutzt du?
Wähle deine App, dann zeigt diese Seite nur die Installation für diese App
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the codebase-to-course folder again. The ZIP must have a codebase-to-course folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick codebase-to-course.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 12. Nov. 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Kopiere diesen Satz und füge ihn in einen Claude Code-Chat ein
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code neu starten, dann /codebase-to-course tippen oder eine passende Aufgabe stellen; Claude nutzt den Skill
Checked against official docs 12. Nov. 2026 · Source: code.claude.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md
git clone --depth 1 https://github.com/zarazhangrui/codebase-to-course.git /tmp/popnx-skill-zarazhangrui-codebase-to-course-ff8837e && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-zarazhangrui-codebase-to-course-ff8837e/.' ~/.claude/skills/codebase-to-courseSelbst installierte Skills funktionieren in der ChatGPT-Desktop-App, in Codex CLI und in der Codex-Erweiterung für die IDE · ChatGPT im Web und auf dem Handy kann selbst installierte Skills nicht nutzen, nur Skills, die mit einem Plugin aus dem Verzeichnis kommen
Die ChatGPT-Desktop-App enthält Codex, und Codex liest Skills aus dem Ordner ~/.agents/skills
Öffne Codex in der ChatGPT-Desktop-App und füge diesen Satz in den Chat ein
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Lege den Ordner codebase-to-course unter ~/.agents/skills/codebase-to-course ab
~ ist dein Home-Ordner ($HOME)
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md
git clone --depth 1 https://github.com/zarazhangrui/codebase-to-course.git /tmp/popnx-skill-zarazhangrui-codebase-to-course-ff8837e && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-zarazhangrui-codebase-to-course-ff8837e/.' ~/.agents/skills/codebase-to-courseChecked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com
Selbst installierte Skills funktionieren hier nicht, nur Skills, die mit einem Plugin aus dem Verzeichnis kommen
Um diesen Skill mit ChatGPT zu nutzen, verwende die ChatGPT-Desktop-App wie oben beschrieben
Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com
Kopiere diesen Satz und füge ihn in einen Codex-Chat ein · Funktioniert in Codex in der ChatGPT-Desktop-App, in Codex CLI und in der IDE-Erweiterung
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex erkennt neu installierte Skills selbst; wenn einer nicht erscheint, starte Codex neu · So nutzt du ihn: In ChatGPT @ tippen und den Skill wählen · in Codex CLI oder der IDE-Erweiterung /skills ausführen oder $ und den Skill-Namen tippen
Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md
git clone --depth 1 https://github.com/zarazhangrui/codebase-to-course.git /tmp/popnx-skill-zarazhangrui-codebase-to-course-ff8837e && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-zarazhangrui-codebase-to-course-ff8837e/.' ~/.agents/skills/codebase-to-courseKopiere diesen Satz und füge ihn in einen Cursor-Chat ein
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Im Agent-Chat von Cursor / tippen und codebase-to-course wählen
Checked against official docs 12. Nov. 2026 · Source: cursor.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md
git clone --depth 1 https://github.com/zarazhangrui/codebase-to-course.git /tmp/popnx-skill-zarazhangrui-codebase-to-course-ff8837e && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-zarazhangrui-codebase-to-course-ff8837e/.' ~/.cursor/skills/codebase-to-courseFür andere Apps, die Skills lesen. Der Satz enthält die Pfade für Claude Code, Codex und Cursor, damit die KI den für deine App wählt · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 12. Nov. 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Andere Apps mit Agent Skills (etwa Gemini CLI oder GitHub Copilot) nutzen andere Ordner. Sieh in deren Anleitung nach und kopiere den Ordner mit der SKILL.md dorthin.
Skill-Ordner am 11. Nov. 2026 mit den offiziellen Anleitungen von Claude Code, Codex und Cursor geprüft
✓ Befehle geprüft am 17. Nov. 2026
Der folgende Text stammt aus dem Repo des Anbieters, nicht von PopNx MCP
Die ersten 8.000 Zeichen · Ganze Datei auf GitHub öffnen
---
name: codebase-to-course
description: "Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'turn this into a course,' 'explain this codebase interactively,' 'teach this code,' 'interactive tutorial from code,' 'codebase walkthrough,' 'learn from this codebase,' or 'make a course from this project.' This skill produces a stunning, self-contained HTML file with scroll-based navigation, animated visualizations, embedded quizzes, and code-with-plain-English side-by-side translations."
---
# Codebase-to-Course
Transform any codebase into a stunning, interactive course. The output is a **directory** containing a pre-built `styles.css`, `main.js`, per-module HTML files, and an assembled `index.html` — open it directly in the browser with no setup required (only external dependency: Google Fonts CDN). The course teaches how the code works through scroll-based modules, animated visualizations, embedded quizzes, and plain-English translations of code.
## First-Run Welcome
When the skill is first triggered and the user hasn't specified a codebase yet, introduce yourself and explain what you do:
> **I can turn any codebase into an interactive course that teaches how it works — no coding knowledge required.**
>
> Just point me at a project:
> - **A local folder** — e.g., "turn ./my-project into a course"
> - **A GitHub link** — e.g., "make a course from https://github.com/user/repo"
> - **The current project** — if you're already in a codebase, just say "turn this into a course"
>
> I'll read through the code, figure out how everything fits together, and generate a beautiful single-page HTML course with animated diagrams, plain-English code explanations, and interactive quizzes. The whole thing runs in your browser — no setup needed.
If the user provides a GitHub link, clone the repo first (`git clone <url> /tmp/<repo-name>`) before starting the analysis. If they say "this codebase" or similar, use the current working directory.
## Who This Is For
The target learner is a **"vibe coder"** — someone who builds software by instructing AI coding tools in natural language, without a traditional CS education. They may have built this project themselves (without looking at the code), or they may have found an interesting open-source project on GitHub and want to understand how it's built. Either way, they don't yet understand what's happening under the hood.
**Assume zero technical background.** Every CS concept — from variables to APIs to databases — needs to be explained in plain language as if the learner has never encountered it. No jargon without definition. No "as you probably know." The tone should be like a smart friend explaining things, not a professor lecturing.
**Their goals are practical, not academic:**
- Have enough technical knowledge to effectively **steer AI coding tools** — make better architectural and tech stack decisions
- **Detect when AI is wrong** — spot hallucinations, catch bad patterns, know when something smells off
- **Intervene when AI gets stuck** — break out of bug loops, debug issues, unblock themselves
- Build more advanced software with **production-level quality and reliability**
- Be **technically fluent** enough to discuss decisions with engineers confidently
- **Acquire the vocabulary of software** — learn the precise technical terms so they can describe requirements clearly and unambiguously to AI coding agents (e.g., knowing to say "namespace package" instead of "shared folder thing")
**They are NOT trying to become software engineers.** They want coding as a superpower that amplifies what they're already good at. They don't need to write code from scratch — they need to *read* it, *understand* it, and *direct* it.
## Why This Approach Works
This skill inverts traditional CS education. The old model is: memorize concepts for years → eventually build something → finally see the point (most people quit before step 3). This model is: **build something first → experience it working → now understand how it works.**
The learner already has context that traditional students don't — they've *used* the app, they know what it does, they may have even described its features in natural language. The course meets them where they are: "You know that button you click? Here's what happens under the hood when you click it."
Every module answers **"why should I care?"** before "how does it work?" The answer to "why should I care?" is always practical: *because this knowledge helps you steer AI better, debug faster, or make smarter architectural decisions.*
The directory-based output is intentional: separating CSS/JS from content means AI never regenerates boilerplate, each module is written independently (keeping output size small and quality high), and the assembled `index.html` works offline with zero setup.
---
## The Process
### Phase 1: Codebase Analysis
Before writing course HTML, deeply understand the codebase. Read all the key files, trace the data flows, identify the "cast of characters" (main components/modules), and map how they communicate. Thoroughness here pays off — the more you understand, the better the course.
**What to extract:**
- The main "actors" (components, services, modules) and their responsibilities
- The primary user journey (what happens when someone uses the app end-to-end)
- Key APIs, data flows, and communication patterns
- Clever engineering patterns (caching, lazy loading, error handling, etc.)
- Real bugs or gotchas (if visible in git history or comments)
- The tech stack and why each piece was chosen
**Figure out what the app does yourself** by reading the README, the main entry points, and the UI code. Don't ask the user to explain the product — they may not be familiar with it either. The course should open by explaining what the app does in plain language (a brief "here's what this thing does and why it's interesting") before diving into how it works. The first module should start with a concrete user action — "imagine you paste a YouTube URL and click Analyze — here's what happens under the hood."
### Phase 2: Curriculum Design
Structure the course as **4-6 modules**. Most courses need 4-6. Only go to 7-8 if the codebase genuinely has that many distinct concepts worth teaching. Fewer, better modules beat more, thinner ones.
The arc always starts from what the learner already knows (the user-facing behavior) and moves toward what they don't (the code underneath). Think of it as zooming in: start wide with the experience, then progressively peel back layers.
| Module Position | Purpose | Why it matters for a vibe coder |
|---|---|---|
| 1 | "Here's what this app does — and what happens when you use it" | Start with the product (what it does, why it's interesting), then trace a core user action into the code. Grounds everything in something concrete. |
| 2 | Meet the actors | Know which components exist so you can tell AI "put this logic in X, not Y" |
| 3 | How the pieces talk | Understand data flow so you can debug "it's not showing up" problems |
| 4 | The outside world (APIs, databases) | Know what's external so you can evaluate costs, rate limits, and failure modes |
| 5 | The clever tricks | Learn patterns (caching, chunking, error handling) so you can request them from AI |
| 6 | When things break | Build debugging intuition so you can escape AI bug loops |
| 7 | The big picture | See the full architecture so you can make better decisions about what to build next |
This is a **menu, not a checklist**. Pick the modules that serve the codebase — a simple CLI tool needs 4, not 7. Adapt the arc to the codebase's complexity.
**The key principle:** Every module should connect back to a practical skill — steering AI, debugging, making dFragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.