ljg-map
Analyzes user manuscripts through the epistemic lens of "Learning View", extracting concepts, criteria of distinction, and conditional connections to construct an accessible formalized knowledge map based on the manuscript's intrinsic relationships. Each node includes a plain-language definition, a concise formula, and concrete semantics, without imposing a preset hierarchy on the graph. USE WHEN the user invokes /ljg-map, or requests to map an article, note, or speech draft into a formalized map, cognitive terrain, or concept criteria and relationship diagram. NOT FOR standard summaries, paragraph-by-paragraph rewrites, geographic maps, or standalone formula proofs.
1How It Works & Mechanism
Core Mechanism: Leverages the concept / criterion / connection perspective of "Learning View" to discern the underlying knowledge structure of user manuscripts.
用《学习观》关于概念、判别模型和联结模型的理解,看到文稿背后的知识结构
Workflow Routing: Read Workflows/Map.md when generating or revising a map; read Examples.md when calibrating expression scale.
从文稿生成地图,或修订已有地图
The epistemic lens is merely a perspective: The alignment across concrete / conceptual / applied layers is an evaluation background, not fixed graph layers or steps.
具象、概念与应用的对应帮助检查知识是否接通,不构成固定的三个图层、三个栏目或必经步骤。
Nodes must originate from the current manuscript; applying rigid templates is prohibited.
**节点来自当前文稿。** 不把任何文章都画成「经验—抽象—概念—记忆—学习」
Prioritize "Chinese Name + Short Formula" for formalization, without measuring by the sheer volume of symbols.
**形式化不以符号数量计。** 优先「中文名称 + 短公式」。
Semantic Discipline: Arrows carry semantic meaning; definition, classification, causality, and other relationship types must not be conflated.
**箭头有语义。** 定义、归类、计算、相关、因果、类比、推断和反馈不能混作一种关系
Every node must be accompanied by a plain-language definition, a short formula, and concrete semantics (specified by the main workflow document).
**白话定义**:它是什么,边界在哪里。
Delivery Convention: Deliver Markdown + Mermaid + readable formulas within the conversation by default; do not write to notes or publish by default.
默认直接在对话中交付 Markdown、Mermaid 和可读公式。
Read-back Standard: Read back the graph, node explanations, and original text before delivery; do not treat valid syntax as visual acceptance.
能解析的图不等于正确或易读的图。
2Core Capabilities
4Recommended Governance & Evidence
- SKILL.md: Pure prompt instructions and rule text; no script execution or external impact
5Second-Pass Verification
- [ok] 四文件角色与 internal_assets — SKILL.md(入口)+ Workflows/Map.md(主流程)+ Examples.md(样例)+ agents/openai.yaml(界面元数据)逐一可定位,路径与 §1 清单一致。
- [ok] 反模板化纪律一致 — SKILL.md「知识观是洞察视角,图形由材料决定」与 Workflows/Map.md「不是排版要求」相互印证。
- [ok] 节点解释最小集 — Workflows/Map.md「每个节点的可用定义」给出白话定义/短公式/具体语义/必要边界四项,与 SKILL.md 成品约定一致。
- [ok] 无脚本/网络/凭证 — 四文件均为 markdown/yaml 文本,风险扫描六类零命中,scripts_executed/network_calls/credential_reads 据实留空。
- [discrepancy] 校准取数未在扫描中体现 — 风险扫描六类零命中,但 Workflows/Map.md 允许用「当前环境可用的来源工具」做事实校准;该调用非 skill 自带依赖、工具与出网范围由宿主决定,故 external_deps 留空并在此记录。
- [ok] 读回标准已纳入 — Workflows/Map.md「读回标准」要求交付前读回图/节点解释/原文,并声明语法通过≠视觉验收,已写入 how_it_works 第 9 条。
6Verdict & Scenarios
00bf29b976102eb6…