Skip to content
Back to skills

Learn Mode

ASecurity

Teach a code, SWE, or CS concept using a fixed six-part shape (snippet, what it does, why it's here, formal name, general problem it solves, connections), then record it in the user's personal knowledge wiki at ~/dev-knowledge/. Use this whenever the user says yes to a "want to pause and learn" offer from the Learning Journal protocol, invokes /learn-mode directly, or asks something like "what does this syntax mean", "explain this pattern", or "teach me this" about a piece of code or a CS/SWE...

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 21, 2026
development

Security analysis

A100/100

Scanned October 21, 2026

npx -y skills add thekusaldarshana/vibecoding-harness --skill learn-mode --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Learn Mode?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Learn Mode
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thekusaldarshana-learn-mode/badge)](https://www.skillsdirectory.com/skills/thekusaldarshana-learn-mode)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: learn-mode
description: Teach a code, SWE, or CS concept using a fixed six-part shape (snippet, what it does, why it's here, formal name, general problem it solves, connections), then record it in the user's personal knowledge wiki at ~/dev-knowledge/. Use this whenever the user says yes to a "want to pause and learn" offer from the Learning Journal protocol, invokes /learn-mode directly, or asks something like "what does this syntax mean", "explain this pattern", or "teach me this" about a piece of code or a CS/SWE concept they're unfamiliar with — even if they don't say "learn-mode" explicitly.
---

# /learn-mode

## Before teaching

1. Check `~/dev-knowledge/index.md` for whether this concept already has a
   file and what status it's at (`unseen` / `introduced` / `practiced` /
   `solid`). If a file exists, read it first — extend or correct it,
   never re-teach from zero something already `practiced` or `solid`.
2. Teach it right here, in whichever session or project raised the
   question. Do not offer to switch to a separate `~/dev-knowledge`
   session — that costs the exact code context that made this worth
   teaching, and buys nothing: reading and writing `~/dev-knowledge/`
   files by absolute path works the same regardless of which directory
   the current session is rooted in.

## The teaching shape — always these six parts, in this order

1. **The snippet** — the actual code or example that raised this, verbatim.
2. **What it does** — plainly, functionally.
3. **Its purpose here** — why this specific snippet needed it.
4. **Its name** — the formal term, so it's searchable independently later.
5. **The problem it solves** — the general class of problem, beyond this
   one snippet.
6. **What it connects to** — named links to related concepts already in
   the wiki.

Stay anchored to the real code in front of you. Never substitute a generic
tutorial example when a real one from the user's own work is available.

## After teaching

Create or update `~/dev-knowledge/<concept-name>.md` with the six parts
above, link it from `index.md` under the right section (Language syntax /
Frameworks / CS & SWE theory), and set its status.

If this session revealed that something already in the wiki was wrong,
outdated, or contradicted by what was just taught, correct or remove that
material now. Never leave an old and a new version of the same
understanding sitting side by side.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.