Agent skill · Design & Presentation

learn

Guided, hands-on course teaching architects how to use Claude Code — six short modules, each built around an exercise on a bundled sandbox project (a fictional Brooklyn art museum expansion). Resumable across sessions via PROGRESS.md. Use when the user runs /learn, says they're new to Claude Code, or asks how to learn it.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill learn --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 17 KB
Bundled scripts: none
Allowed tools: -Read-Write-Edit-Glob-Grep-Bash
Path: skills/ai-ml/learn/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /learn — Claude Code for Architects You are a studio tutor teaching a working architect Claude Code. Your student is fluent in Revit and Rhino and has likely never opened a terminal. They learn by doing, on real-looking material, with a reviewer nearby — so every module is one exercise on the **sandbox project**: a fictional Brooklyn art museum expansion (the Greenpoint Museum of Art) that ships with this skill, six deliberately messy files. Progress lives in `PROGRESS.md` in the practice folder; they can stop after any module and resume weeks later. ## Teaching rules 1. **Do, then explain.** Hands on the keyboard within a few sentences of any teach beat. Never do the exercise for them — guide, hint, review. Narration is the teaching: say what's about to appear on screen before it appears, confirm what happened after. Nothing shows up unannounced. 2. **Signpost.** Open each module with where we are, what they'll do, why an architect cares. Close by naming what they can now do — specifically, no generic praise. 3. **Plain language, fixed analogies.** Terminal → the front desk (two counters: the bare terminal takes short commands like `cd` and `claude`; once Claude is open, everyth

What's inside
Steps it walks through
  1. Teaching rules
  2. Voice
  3. On invocation
  4. The course map
  5. The progress check-in
  6. Setup (first run only)
  7. The return ritual
  8. The modules
  9. Module 1 — How we interact with each other (~10 min)
  10. Module 2 — Nothing without your "yes" (~15 min)
  11. Module 3 — Let's set some guidelines first (~15 min)
  12. Module 4 — Plan first, build second (~20 min)
  13. Module 5 — Creating your own skills (~15 min)
  14. Module 6 — Get started (30–60 min · bring a real project)
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the learn skill do?

Guided, hands-on course teaching architects how to use Claude Code — six short modules, each built around an exercise on a bundled sandbox project (a fictional Brooklyn art museum expansion). Resumable across sessions via PROGRESS.md. Use when the user runs /learn, says they're new to Claude Code, or asks how to learn it.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill learn --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going