Markstream Migration
Audit and migrate existing Markdown rendering to Markstream, or upgrade a...
Install
npx skills add Simon-He95/markstream-vue --skill markstream-migration -g -a claude-code -y- Repository
- Simon-He95/markstream-vue3k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,856 tokens
- Runs scripts
- No, instructions only
What it does
Audit and migrate existing Markdown rendering to Markstream, or upgrade a markstream-vue 1.x integration to 2.x. Use when Codex needs to replace another renderer, classify direct vs custom vs plugin-heavy adoption, preserve behavior during adoption, migrate custom renderers into scoped Markstream overrides, decide when `nodes` streaming is worth adopting, or replace removed 1.x code-block dependencies, APIs, preview payloads, and parser types.
Markstream Migration
Use this skill when a repo already renders Markdown and the task is either to adopt Markstream safely or to upgrade an existing markstream-vue 1.x integration to 2.x.
Choose The Migration Route
Inspect package.json, the lockfile, imports, and renderer props before changing code.
- If the repo already depends on
markstream-vue1.x, read references/vue-1x-to-2x.md and follow Route B. Confirm the package dependency instead of routing only from shared names such asMarkdownCodeBlockNodeorInternalParseOptions, which can also appear in other adapters. - Otherwise, when replacing
react-markdown,markdown-it,marked, or another renderer with a Markstream package, read references/adoption-checklist.md and follow Route A. - If both apply, complete the 1.x to 2.x package and API upgrade first, then audit the separate renderer replacement as an adoption task.
