@wangxueqi/dsh-client-ui-knowledge-cards
将对话内容转化为知识卡片：概念、流程图、对比等，适用于 Web
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:wangxueqi00/dsh-client-ui-knowledge-cards#72f87efe45960e5ec1f89caa460875dca7cd8998Client Ui Knowledge Cards 以 @wangxueqi/dsh-client-ui-knowledge-cards 发布，当前版本为 0.1.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Turn any conversation in your DeepSeek Harness Web GUI into clean, textured knowledge cards — concepts, flowcharts, comparisons, summaries, mind maps, quotes, checklists, timelines and FAQs — generated by the agent, previewed in a tabbed gallery, and downloadable in multiple formats.
prefers-color-schemequote, checklist, timeline, and faq```facts JSON block; the client merges and deduplicates it into a session-scoped store, then deterministically builds those two cards from the whole historytimeline and checklist always use the whole historyCurrent release: v0.1.3, published on GitHub and npm with the same version on both platforms.
Compatible DSH versions (unchanged from v0.1.2 — this release targets the same DSH versions):
| DSH version | Date |
|---|---|
0.1.1-rc.2 | 2026-08-21 |
0.1.1-rc.1 | 2026-08-21 |
0.1.0-rc.8 | 2026-08-19 |
0.1.0-rc.7 | 2026-08-17 |
0.1.0-rc.6 | 2026-08-13 |
From npm:
dsh plugin --profile web add @wangxueqi/dsh-client-ui-knowledge-cards
Or from GitHub (main branch):
dsh plugin --profile web add github:wangxueqi00/dsh-client-ui-knowledge-cards
Or pinned to a tag:
dsh plugin --profile web add github:wangxueqi00/dsh-client-ui-knowledge-cards#v0.1.3
Then restart:
dsh --profile web
The package declares dsh.bundle, so dsh plugin add activates it as a profile layer automatically — no manual config edits. Build artifacts (lib/) are committed to the repository, so GitHub installs need no build step.
| Type | Icon | Content | Best for |
|---|---|---|---|
| Concept | 💡 | Markdown headings + bullet lists | Definitions and explanations |
| Flowchart | 🔀 | Mermaid graph | Processes and decision flows |
| Comparison | ⚖️ | Markdown table | Side-by-side trade-offs |
| Summary | 📋 | Bullet list | Key takeaways |
| Mind map | 🧠 | Mermaid mindmap | Hierarchical concept maps |
| Quote | ❝ | Markdown blockquotes | Key conclusions and quotes |
| Checklist | ✅ | Markdown task list | Action items and todos |
| Timeline | 🕒 | Mermaid timeline | Chronological events and milestones |
| FAQ | ❓ | Markdown Q&A | Questions and answers |
| Format | Concept / Comparison / Summary / Quote / Checklist / FAQ | Flowchart / Mind map / Timeline |
|---|---|---|
Markdown (.md) | ✅ | ✅ |
HTML (standalone .html) | ✅ | ✅ (Mermaid via CDN) |
JSON (.json) | ✅ | ✅ |
Plain text (.txt) | ✅ | ✅ |
SVG (.svg) | ✅ (text card) | ✅ (rendered diagram) |
The plugin is a single-file browser bundle plus a small host layer:
```card JSON blocks followed by a <!-- knowledge-cards-generated --> completion marker.conversation.session.header.actions slot. The button stays mounted and watches the conversation in the background; when the agent finishes, it parses the card blocks into a module-level store, so closing the dialog never loses state.```facts JSON block; the client merges those facts into a per-session store and builds the two cards deterministically, so whole-history cards stay deduplicated and regenerate without re-reading the conversation.This repository is developed inside a DeepSeek Harness monorepo checkout: the build preset, tsconfig references, and platform module table live there. One physical tree, two views - clone it into the monorepo, or junction your clone onto it:
# inside your DSH checkout: this repo's clone IS the physical tree
git clone https://github.com/wangxueqi00/dsh-client-ui-knowledge-cards.git `
packages/client/ui-knowledge-cards
# optional: keep a convenient view elsewhere
New-Item -ItemType Junction -Path <your-path> -Target <dsh-checkout>\packages\client\ui-knowledge-cards
# then at the monorepo root
pnpm install
Build (from either path - the script resolves the junction):
./scripts/build.ps1 # tsc -b + bundle
./scripts/build.ps1 -Watch # tsc -b + watch
pnpm run bundle # bundle alone also works from the repo path
The same package.json serves development and release alike: real version ranges (^0.1.1-rc.2) link to the workspace packages inside the monorepo (linkWorkspacePackages) and install cleanly from npm/git - no transformation between dev and release forms.
src/
├── index.ts # host layer: system-prompt guidance
├── invariant.ts # invariant companion
└── client/
├── index.ts # plugin entry: apply(), slot registration
├── card-store.ts # module-level card store (persists across dialog open/close)
├── card-generator.ts # card types, themes, prompt builders
├── card-parser.ts # parses ```card blocks from agent output
├── card-data-collector.ts
├── download.ts # MD / HTML / JSON / TXT / SVG export
├── mermaid-renderer.ts
├── locales.ts # zh / en dictionaries
└── components/ # CardButton, CardDialog, CardGallery, CardView, MermaidDiagram
The repo itself is the release vehicle - source, committed lib/ artifacts, and a release-ready package.json all in one place:
./scripts/build.ps1 # 1. build (lib/ lands in the repo)
# 2. bump "version" in package.json
git add .
git commit -m "release: v0.x.y"
git tag v0.x.y
git push origin main --tags # 3. GitHub release
pnpm publish --no-git-checks # 4. npm release
lib/ must stay committed (check .gitignore): the artifacts are what makes dsh plugin add github:... work without a build step.
MIT