concept-atlas-dense-explain 0.2.2 → 0.3.0

package/{skill/assets/template → template}/vite.config.js

@@ -1,4 +1,4 @@
-import { defineConfig } from 'vite';
+import { defineConfig } from 'vite';
 import react from '@vitejs/plugin-react';
 import mdx from '@mdx-js/rollup';
 import { viteSingleFile } from 'vite-plugin-singlefile';
@@ -14,8 +14,8 @@ export default defineConfig({
     react(),
     viteSingleFile(),
   ],
-  build: {
-    outDir: 'dist',
-    emptyOutDir: true,
-  },
-});
+  build: {
+    outDir: 'dist',
+    emptyOutDir: true,
+  },
+});

package/bin/install.mjs

@@ -1,17 +0,0 @@
-#!/usr/bin/env node
-import fs from 'node:fs/promises';
-import path from 'node:path';
-import os from 'node:os';
-import { fileURLToPath } from 'node:url';
-
-const packageRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..');
-const source = path.join(packageRoot, 'skill');
-const args = process.argv.slice(2);
-const targetArg = args.find(arg => arg.startsWith('--target='))?.slice('--target='.length);
-const codexHome = process.env.CODEX_HOME || path.join(os.homedir(), '.codex');
-const target = path.resolve(targetArg || path.join(codexHome, 'skills', 'concept-atlas-dense-explain'));
-
-await fs.mkdir(target, { recursive: true });
-await fs.cp(source, target, { recursive: true, force: true });
-console.log(`Installed concept-atlas-dense-explain to ${target}`);
-console.log('The skill includes a self-contained template under assets/template.');

package/skill/assets/template/scripts/build.mjs

@@ -1,37 +0,0 @@
-import { build } from 'vite';
-import path from 'path';
-import fs from 'fs';
-import { fileURLToPath } from 'url';
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = path.dirname(__filename);
-const rootDir = path.resolve(__dirname, '..');
-
-async function runBuild() {
-  console.log('🚀 开始构建 Concept Atlas 知识讲解页面...');
-
-  try {
-    // 确保 dist 目录存在
-    const distDir = path.resolve(rootDir, 'dist');
-    if (!fs.existsSync(distDir)) {
-      fs.mkdirSync(distDir, { recursive: true });
-    }
-
-    // 执行 Vite 构建
-    await build({
-      root: rootDir,
-      build: {
-        outDir: 'dist',
-        // Always remove stale assets so dist is a self-contained release.
-        emptyOutDir: true,
-      }
-    });
-
-    console.log('✅ 构建成功！产物已生成到 dist/ 目录。');
-  } catch (err) {
-    console.error('❌ 构建失败：', err);
-    process.exit(1);
-  }
-}
-
-runBuild();

package/skill/references/components.md

@@ -1,74 +0,0 @@
-# Component contract
-
-## Structure
-
-```mdx
-<ExplainPage id="topic" title="..." summary="...">
-  <ConceptGraph root="root">
-    <ConceptNode id="root" title="..." level="L0" summary="...">
-      <Definition>...</Definition>
-      <Input>...</Input><Output>...</Output>
-      <Children><ConceptRef id="child" /></Children>
-    </ConceptNode>
-    <ConceptNode id="child" title="..." level="L1" parent="root">...</ConceptNode>
-    <Relation from="child" to="other" type="depends-on" label="依赖" />
-  </ConceptGraph>
-</ExplainPage>
-```
-
-Supported semantic content includes `Overview`, `Definition`, `Mechanism`, `Implementation`, `Example`, `Counterexample`, `Boundary`, `Prerequisite`, `Input`, `Output`, and `Glossary`.
-
-High-value verification components: `LearningObjectives`, `KeyQuestion`, `Evidence(command, observes)`, `Invariant(title)`, `FailureMode(symptom, cause, evidence, remedy)`, and `Tradeoff(options)`.
-
-Presentation components: `Stack`, `Grid`, `Split`, `Tabs`, `Flow`, `Compare`, `DecisionMatrix`, `Timeline`, `FrameworkModel`, `MatrixModel`, `FormulaModel`, `PyramidModel`, `FunnelModel`, `Callout`, `Details`, `RelationMap`, `RelationPath`, `Insight`, and `NoteGrid`.
-
-经典结构模型建议按问题选择，避免重复堆叠：
-
-- `FrameworkModel`：一分为几、多因素并列、阶段、分层或循环；用 `type="elements|stages|layers|cycle"` 区分结构。
-- `MatrixModel`：两个关键元素组成的二维象限，例如重要/紧急、增长率/市场份额。
-- `FormulaModel`：用公式表达变量之间的乘加减关系，例如业绩、价值或行为模型。
-- `PyramidModel`：从基础到顶层的分层归纳，例如学习目标、需求层次或论证结构。
-- `FunnelModel`：从输入到筛选、转化、结果的逐步收敛，例如 AIDA 或销售漏斗。
-
-原有 `Flow`、`DecisionMatrix`、`Compare`、`Timeline` 继续保留，用于兼容已有内容；新内容优先使用上面的模型组件表达“关键元素与结构”的关系。
-
-## Relation types (whitelist — only these render)
-
-Write cross-branch `Relation`s with `type` from this exact list. Any other value renders no styled edge.
-
-| type | label | use for |
-| --- | --- | --- |
-| `prerequisite` | 前置知识 | knowledge required before this concept |
-| `causes` | 因果推动 | one concept triggers a state change in another |
-| `produces` | 产出生成 | a stage outputs an artifact or entity |
-| `uses` | 消费使用 | a concept consumes or calls another |
-| `implements` | 实现关系 | a concrete mechanism implements an abstraction |
-| `contrasts` | 对比关系 | side-by-side contrast (no arrowhead) |
-| `depends-on` | 依赖关系 | runtime/effect depends on an external condition |
-| `exception-of` | 异常/反例 | a boundary case, counterexample, or broken assumption |
-| `precedes` | 时序先后 | pipeline or temporal ordering |
-
-Do **not** write `parent-child` as a `Relation`; the tree edge is generated automatically from `parent` / `Children`. Add a short `label` to every relation so the graph edge is readable.
-
-## Levels L0–L4
-
-| Level | name | role | typical components |
-| --- | --- | --- | --- |
-| `L0` | 全局概览 | system-wide framing and the root claim | `Definition`, `Prerequisite`, `LearningObjectives`, `KeyQuestion`, `Input`/`Output`, `Callout`, `Tabs` |
-| `L1` | 主要阶段 / 子系统 | major lifecycle stage or subsystem | `Definition`, `Input`/`Output`, `Example`, `Children` |
-| `L2` | 局部机制 | concrete mechanism and flow | `Definition`, `Mechanism`, `Details`, `Evidence`, `Invariant`, `Tradeoff`, `FailureMode` |
-| `L3` | 实现细节 | algorithm, data structure, or code | `Definition`, `Example`, `Glossary` |
-| `L4` | 边界与反例 | boundary, exception, or counterexample | `Callout(danger/warn)`, `Example`, `FailureMode` |
-
-## Density targets
-
-Match the exemplar (`assets/template/content/compile-runtime.mdx`):
-
-- 1 `L0` root, 4–5 `L1` branches, 2–3 children per branch, ~15–25 nodes total.
-- Every key node: 3–6 semantic components; `L3`/`L4` nodes may be leaner but still concrete.
-- At least a few nodes per document carry `Evidence`, `Invariant`, or `FailureMode` with a real command/observation.
-- ~8–15 cross-branch `Relation`s, each with a `label`.
-
-## Request priorities
-
-The portable template covers the core `req.md` contract, node exploration, graph view, semantic relations, search, level/relation filters, URL node state, browsing history, keyboard shortcuts, Mermaid zoom, and responsive rendering. Evidence-oriented components and compact tradeoffs cover the highest-value `request.md` enhancements without adding permanent side panels.

package/skill/references/prompting.md

@@ -1,90 +0,0 @@
-# AI prompt guide
-
-Include this contract when asking an AI to generate or revise a dense explanation:
-
-```text
-先通读 content/compile-runtime.mdx（黄金样例），再产出；不要跳过、不要直接覆盖。
-输出语义 MDX，不要输出 CSS、HTML 布局、坐标、SVG 或交互脚本。
-先给一个 L0 根节点，再用 L1/L2/L3/L4 表达结构、机制、实现细节和边界。
-父子层级使用 parent/Children；跨分支含义使用 Relation。
-Relation 的 type 只能是：prerequisite, causes, produces, uses, implements, contrasts, depends-on, exception-of, precedes；每条都要带 label。
-每个关键节点优先提供：summary、Definition、Input/Output、Mechanism、一个 Example，以及 Evidence 或 Boundary。
-只在确实有帮助时使用组件：Flow 表示顺序，Compare/Tradeoff 表示选择，Timeline 表示时间，Evidence 表示验证，Invariant 表示必须保持的条件，FailureMode 表示故障定位。
-首屏只保留核心结论和 3–5 个关键事实；次要解释放进 Details。不要为了“看起来丰富”堆卡片。
-规模对齐样例：1 个根、4–5 个 L1、总计约 15–25 个节点、8–15 条 Relation。
-证据要具体：真实命令、指标或命名的产物，不要泛泛而谈。
-```
-
-## Template availability gate
-
-Use this gate before the contract above:
-
-```text
-先确认当前 skill 目录中的 assets/template 可访问，并读取黄金样例与模板源码。
-如果模板不可访问，立即停止并说明缺少 Concept Atlas 模板；禁止自行用 JSX、HTML、CSS 或普通 Markdown 页面替代。
-模板可访问后，复制完整模板，只修改 content/compile-runtime.mdx，最后运行 npm run validate 和 npm run build。
-交付物必须是模板构建出的 dist/index.html。
-```
-
-## What "good" looks like (from the exemplar)
-
-`assets/template/content/compile-runtime.mdx` is the reference standard. Extract these patterns:
-
-- **Scale**: 1 `L0` + 5 `L1` + ~20 nodes, descending to `L4`.
-- **Titles are claims, not nouns**: 「缺页风暴与抖动」, 「ABI 破坏：能链接，不等于能调用」.
-- **Every node opens with a one-sentence judgment** in `summary`, then 3–6 components.
-- **Concrete evidence**: `readelf -Ws`, `nm -C`, `objdump -dr app.o`, `.bss`, ASLR, build-id.
-- **Semantic relations carry the cross-branch meaning**: `produces`, `precedes`, `causes`, `depends-on`, `exception-of`, each labeled.
-- **Detail is layered**: first screen = core claim + 3–5 facts; deep detail lives in `Details`, `Tabs`, `Glossary`.
-
-## Density targets
-
-| Metric | Target | Thin (failure) |
-| --- | --- | --- |
-| `L0` roots | 1 | 0 or many |
-| `L1` branches | 4–5 | 1–2 |
-| Nodes total | ~15–25 | < 8 |
-| Components per key node | 3–6 | 1 |
-| Cross-branch `Relation`s | 8–15 | 0–3 |
-| Nodes with concrete evidence | several | none |
-| Max depth | `L3`/`L4` | only `L0`/`L1` |
-
-## Component selection
-
-| Information shape | Component |
-| --- | --- |
-| 顺序、阶段、因果链 | `Flow` / `RelationPath` |
-| 两到四个对象的同维度比较 | `Compare` |
-| 方案、收益、代价、适用条件 | `Tradeoff` / `DecisionMatrix` |
-| 时间先后 | `Timeline` |
-| 可执行命令和观察结果 | `Evidence` |
-| 必须保持的条件 | `Invariant` |
-| 症状到原因和修复 | `FailureMode` |
-| 次要细节或长解释 | `Details` |
-
-Avoid using more than one primary presentation component in a single node unless the information shapes are genuinely different. Prefer short prose around one useful visual structure over a stack of decorative blocks.
-
-## Minimal generation skeleton
-
-```mdx
-<ConceptNode id="mechanism" title="机制：输入如何在约束下变成输出" level="L2" parent="structure" summary="一句话结论">
-  <Definition>它是什么，以及为什么重要。</Definition>
-  <Mechanism>输入 → 转换 → 输出。</Mechanism>
-  <Example title="一个具体案例">名称 + 数值 + 结果，而不是泛指。</Example>
-  <Evidence command="tool --inspect target" observes="验证哪个不变量或产物。" />
-  <Boundary>何时不成立，或哪些实现细节会改变结论。</Boundary>
-</ConceptNode>
-```
-
-## Anti-patterns
-
-- **Thin graph**: a handful of nodes with one paragraph each. Fix by adding `L2`/`L3`/`L4` depth.
-- **Noun titles / no judgment**: `"缓存"` instead of `"缓存一致性与内存序"`; `summary` missing or restating the title.
-- **Generic filler**: "性能会受到影响" instead of a named command, metric, or artifact.
-- **Card stacking**: five decorative blocks with no conclusion, evidence, or limitation.
-- **Invented types**: `Relation type="related"` — not in the whitelist, renders nothing.
-- **Prose instead of structure**: cross-branch links described in a paragraph instead of a labeled `Relation`.
-
-## Before returning the result
-
-Verify the self-check list in `SKILL.md`. In short: 1 root, claim titles, one-line summaries, 3–6 components per key node, concrete evidence, whitelisted relations, layered detail, no layout in MDX, template builds.