# Markstream Migration

Audit and migrate existing Markdown rendering to Markstream, or upgrade a...

- Repository: https://github.com/Simon-He95/markstream-vue (3046 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Simon-He95/markstream-vue --skill markstream-migration -g -a claude-code -y`
Codex: `npx skills add Simon-He95/markstream-vue --skill markstream-migration -g -a codex -y`
Cursor: `npx skills add Simon-He95/markstream-vue --skill markstream-migration -g -a cursor -y`
Gemini CLI: `npx skills add Simon-He95/markstream-vue --skill markstream-migration -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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-vue` 1.x, read [references/vue-1x-to-2x.md](references/vue-1x-to-2x.md) and follow **Route B**. Confirm the package dependency instead of routing only from shared names such as `MarkdownCodeBlockNode` or `InternalParseOptions`, 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](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.

## Route A: Adopt Markstream From Another Renderer

The rest: https://github.com/Simon-He95/markstream-vue/blob/HEAD/.agents/skills/markstream-migration/SKILL.md