← ClaudeAtlas

knowledge-point-treelisted

Build a flat, exhaustive "point tree" of every enumerable knowledge point in a bounded body of material (a textbook, a certification syllabus, a spec, an API surface, a legal code), so a learner facing a brand-new field can see the whole board at once instead of drowning in unknown unknowns. Use this whenever someone says they are starting a new field and feel lost, can't tell where things belong, keep confusing similar-sounding terms, want a "framework" or "整体框架" or "knowledge map" of a subject, are prepping for a certification exam, or hand over a textbook/PDF/spec and ask what's in it. Also use when someone asks to summarize all the numbered lists, categories, or classifications in a document. Do NOT wait for the words "point tree" — the trigger is the feeling of being overwhelmed by an unfamiliar domain, or the presence of a bounded authoritative source that needs mapping.
SYQ1001/knowledge-point-tree · ★ 2 · Data & Documents · score 65
Install: claude install-skill SYQ1001/knowledge-point-tree
# Knowledge Point Tree ## What this solves The hardest moment in a new field is not difficulty — it's **not knowing what you don't know**. A learner reads chapter 9, then chapter 16, and has no idea the two are talking about the same concept at different levels. Similar terms blur. Nothing has a home. A point tree fixes orientation before it fixes knowledge. It is a **flat, exhaustive inventory of every enumerable group** in the material — "the seven principles of X", "the four classifications of Y", "the three layers of Z" — organized by nothing but chapter, with all sub-numbering flattened away. It is not a table of contents. A TOC tells you a section exists. A point tree tells you **what is inside every section, at the grain the field itself uses**. The learner ends up with initial literacy: they can now hear an unfamiliar term and place it. That is the deliverable. ## Why it works Understanding the mechanism matters more than following the steps, because it tells you what to do when the material doesn't fit the recipe. **Learning a field is not a sapling growing into a tree.** It is not trunk first, then branches, then leaves. Everything comes up faintly at once — like a progressively-loaded image that appears whole at low resolution and then sharpens all over, rather than rendering top to bottom. The point tree is that low-resolution first pass: the entire field, visible at once, in no detail whatsoever. This has empirical backing. Ausubel's *advance organizer*