Build To Learn — Testing skill for Claude Code

Build to Learn

**English** | [简体中文](README.zh-CN.md)

A Claude Code skill for people who want to *actually understand* the thing they're building — not just end up holding code they can't explain.

This file is for humans. `SKILL.md` and `references/` are the rulebook Claude follows; you never need to read them.

What this is

You want to build something, and you want to genuinely learn the tech behind it. This skill handles that.

It exists to prevent one specific failure: the AI one-shots the whole thing, the app runs, and you learned nothing. So the rule here is inverted — **learning is the goal, and the thing you build is the evidence that you learned it.**

Claude writes all the code. You don't need to know how to program.

Install

Requires [Claude Code](https://claude.com/claude-code).

git clone  ~/.claude/skills/build-to-learn

`~/.claude/skills/` makes it available everywhere. To scope it to one project, drop it in that project's `.claude/skills/` instead.

Where your notes live: it asks you

On first launch Claude asks one question — where should your learning notes go? Default is `~/Documents/Build To Learn`. Answer once, it creates the folder, writes `config.md`, and never asks again.

Any folder works. If you use Obsidian, point it inside your vault — the Mermaid diagrams and collapsible self-quizzes render natively. If you don't, no problem: they're plain Markdown files.

Want to move it later? Edit the one line in `config.md`, or just tell Claude. That file is gitignored, so pulling updates won't clobber your path.

Getting started

Type `/build-to-learn`, or just say "walk me through building X — I want to actually learn it."

On your very first run you have no projects yet, so Claude offers two options: start a new project, or read this tutorial first.

Every launch after that, it lists your existing projects and where each one is stuck, and asks which to continue. **Continuing never re-runs setup** — it rea