Using the understanding of concepts, discrimination models, and connection models from *A View of Learning*, see the knowledge structure behind the manuscript: which words have clear referents, on what basis real-world objects are classified under them, and under what conditions the relationships among concepts hold. Draw the structure you see; formalization is responsible for reducing ambiguity, while plain language and examples are responsible for making the relationships understandable and usable.
Workflow Routing
| Request | Execute |
|---|---|
| Generate a map from the manuscript, or revise an existing map | Read Workflows/Map.md |
| Need to calibrate formula density, node explanations, and source boundaries | Read as needed Examples.md; learn the way of expression, do not apply the subject matter and nodes mechanically |
Gotchas
- The view of knowledge is an insight perspective; the diagram is determined by the material. The correspondence among the concrete, the conceptual, and the applied helps check whether knowledge is connected; it does not constitute fixed three layers, three columns, or required steps. If categories intersect, draw an intersecting relationship; if there is feedback, draw a loop; only draw hierarchy when the material truly has hierarchy.
- Nodes come from the current manuscript. Do not draw every article as "experience—abstraction—concept—memory—learning"; only when the article itself discusses these concepts do they become content nodes. Discrimination and verification can be written on edges or in node explanations, and need not always occupy a box.
- A map is not a long text converted into formulas. The finished product first lets readers see the load-bearing relationships, then explains the nodes in the diagram. It cannot provide only a list of concepts, a long table, or a string of formulas without a map.
- Formalization is not measured by the number of symbols. Prioritize "Chinese name + short formula". Define symbols before using them, and do not invent another set of graph-theoretic metalanguage to describe an article that is originally very simple.
- Keep classification and prediction separate. "Has a circle" can define a class; "this class will gain points" is another relationship that requires grounds. Satisfying the classification condition does not automatically prove the prediction holds, nor can it infer that the opposite class has the opposite result.
- Arrows have semantics. Definition, classification, calculation, correlation, causation, analogy, inference, and feedback cannot be mixed as one kind of relationship; distinguish them with short edge labels and necessary conditions. Conjectures are still marked as conjectures.
- The completeness of the diagram cannot rely on fabrication. If the manuscript lacks discrimination criteria, examples, or verification methods, mark the gap in the corresponding position. Supplementary teaching examples, application ideas, and feasibility judgments must be distinguished from statements in the original text.
Finished product conventions
By default, deliver Markdown, Mermaid, and readable formulas directly in the conversation. When the user requests saving, a specific format, or modification of an existing artifact, deliver according to their specification; this skill does not by default write notes, overwrite the original text, or publish.
The main diagram shows the knowledge relationships specific to this manuscript, without presupposing the number of layers, shapes, or a unified application process. Keep the main relationships easy to read; secondary branches can be placed in supplementary diagrams with connection positions or in a labeled table. Every node in each diagram can be found in the explanation with the same number or name, as well as its definition, formula, semantics, and concrete correspondence.
Examples
/ljg-map <文稿或文件路径>: After reading the actual content, draw the knowledge structure of the manuscript, explain each node, and clarify the key relationships with appropriate concrete correspondences.把这篇文章的概念、判别和联结画清楚,别改写文章: Preserve the author's main reasoning, parallel structures, and important disagreements; indicate conditions and uncertainties in the sources at the arrows.这张图太难懂,重新画: Reduce symbol and main-figure clutter, use one appropriate example throughout; preserve conditions that would change the judgment, and do not trade away arguments for superficial simplicity.