Docs suggestion: a "Migrating from Claude Code" guide (most of it is already free)

[sjh9714]

A large share of the people trying DSH this week come from Claude Code, and the single most common question shape in discussions is some form of "how do I bring my setup over". The pleasant surprise is that DSH already did most of the work, CLAUDE.md is a default instruction candidate, SKILL.md loads as is, mcp__server__tool names are identical, and dsh-hooks-claude-code runs existing hooks configs unchanged. But none of that is discoverable in one place in the docs, people find it out by reading source or by accident.

Suggestion, a short "Migrating from Claude Code" page under docs/user/guide covering, per asset type, what is native, what needs one manual step, and what has no equivalent (sessions, slash commands, permission allowlists). Since external PRs are not accepted right now, offering research instead of a patch. We measured every asset type against the rc.6 source and published it as a compatibility matrix, feel free to lift any of it into official docs, no attribution needed:

https://github.com/sjh9714/dsh-movein/blob/main/docs/compat.md

Community tooling already covers the automatable parts (dsh-chat-import for conversation history, dsh-movein for config/skills/MCP/hooks), the docs gap is the map itself.

中文：建议在官方文档加一页「从 Claude Code 迁移」。DSH 其实已经原生消化了大半（CLAUDE.md 默认读取、SKILL.md 原样兼容、MCP 工具名一致、hooks 有官方桥），但这些散落在源码里，没有一处能看全。我们按 rc.6 源码逐项实测整理了对照表（上面链接，含中文摘要），官方文档随意取用，无需署名。

[weijiafu14]

This matrix is useful. One additional migration dimension is the extension ecosystem: after moving instructions, skills, MCP and hooks, users still tend to miss search, memory, subagents and vision packages from their previous setup.

pi2dsh lets DSH load published Pi packages through the normal DSH plugin workflow, without converting or patching each package:

dsh plugin --profile web add pi2dsh
dsh plugin --profile web add <pi-package>

The repository now includes real DSH-loop examples for vision, Codex image generation/editing, side conversations, MCP, subagents, provider routes and cross-process memory. It may be useful as an “ecosystem migration” entry in the guide alongside the asset-level matrix: https://github.com/weijiafu14/pi2dsh