Markstream Vue2 CLI
Developmentmarkstream-vue2-cliMarkstream Vue2 CLI is an Agent Skill for development published in the Simon-He95/markstream-vue repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Integrate markstream-vue2 into a Vue 2 Vue CLI or Webpack 4 app. Use when Codex needs Webpack 4-friendly setup, CDN worker fallbacks for Mermaid or KaTeX, `dist/index.css` imports, Vue 2 composition-api shims, or safer code block defaults that avoid fragile Monaco worker setups.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Simon-He95/markstream-vue/blob/HEAD/.agents/skills/markstream-vue2-cli/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/markstream-vue2-cli, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Markstream Vue 2 CLI
Use this skill when the host app is Vue 2 on Vue CLI or another Webpack 4-style stack.
Workflow
- Confirm the repo uses Vue 2 plus Vue CLI or Webpack 4-era tooling.
- Install
markstream-vue2and only the peers required for the requested features. - Import
markstream-vue2/dist/index.cssin the app shell. - Avoid Vite-style
?workerimports.- Use
createKaTeXWorkerFromCDN(...)andcreateMermaidWorkerFromCDN(...)when workers are needed.
- Use
- Prefer stable code block defaults over brittle Monaco wiring.
MarkdownCodeBlockNodeplusstream-markdownis safer than Monaco in Webpack 4-era repos.- For AI chat or streaming UIs, keep
contentand use built-in smooth streaming first.smooth-streaming="auto"is the default and activates whentypewriter=trueormax-live-nodes <= 0.typewriteronly controls the blinking cursor and defaults tofalse.fadecontrols node enter and streamed-text fade animations and defaults totrue.
- Streaming vs recovering history: in chat UIs the same
MarkdownRenderstarts streaming and later switches to history whenfinal=true.- Streaming:
smooth-streaming="auto",:fade="false",typewriter=true. Smooth pacing handles gradual appearance; fade would flicker. - Recovering history:
:smooth-streaming="false",:fade="true",typewriter=false. Content is already complete — pacing would slow it down, but fade gives a polished entry animation. - Dynamic switch:
:smooth-streaming="isStreaming ? 'auto' : false",:fade="!isStreaming".
- Streaming:
- Move to
nodes+finalonly for worker-preparsed content, shared AST stores, or custom AST control. - Remember that
html-policynow defaults tosafe, and Mermaid strict mode is on by default throughmermaid-props.
- Validate with the smallest useful local dev or build command.
Default Decisions
- Treat Monaco and worker-heavy setups as opt-in and fragile on Webpack 4.
- Prefer CDN workers over bundler workers for Mermaid and KaTeX.
- Keep the Vue 2 composition-api shim explicit when the repo is on Vue 2.6.
- Keep
html-policy="safe"and Mermaid strict mode unless the task is preserving trusted legacy rendering. - If a trusted surface needs older behavior, use
html-policy="trusted"and:mermaid-props="{ isStrict: false }"only on that surface and explain why.
Useful Doc Targets
docs/guide/vue2-quick-start.mddocs/guide/vue2-installation.mddocs/guide/troubleshooting.md