원클릭으로 Manus에서 모든 스킬 실행

markstream-vue2-vite

스타2,779

포크171

업데이트2026년 5월 11일 07:50

Integrate markstream-vue2 into a Vue 2 plus Vite app. Use when Codex needs Vite-friendly worker imports, `?worker` or `?worker&inline` setup for Mermaid or KaTeX, modern CSS ordering, or Vue 2 compatibility in a Vite-based repository.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Simon-He95

Simon-He95/markstream-vue

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Markstream Vue 2 Vite

Use this skill when the host app is Vue 2 and the bundler is Vite.

Workflow

Confirm the repo is Vue 2 with Vite-based tooling.
Install markstream-vue2 plus only the requested optional peers.
Import markstream-vue2/index.css after resets.
Use Vite worker imports when the repo needs bundled workers.
- markstream-vue2/workers/... ?worker or ?worker&inline patterns are allowed here.
Keep Composition API decisions explicit for Vue 2.6 repos.
- For AI chat or streaming UIs, keep content and use built-in smooth streaming first.
  - smooth-streaming="auto" is the default and activates when typewriter=true or max-live-nodes <= 0.
  - typewriter only controls the blinking cursor and defaults to false.
  - fade controls node enter and streamed-text fade animations and defaults to true.
- Streaming vs recovering history: in chat UIs the same MarkdownRender starts streaming and later switches to history when final=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".
- Move to nodes + final only for worker-preparsed content, shared AST stores, or custom AST control.
- Remember that html-policy now defaults to safe, and Mermaid strict mode is on by default through mermaid-props.
Validate with the smallest useful Vite dev or build command.

Default Decisions

Prefer bundled workers over CDN workers in Vite-based Vue 2 repos.
Keep UnoCSS or Tailwind resets before Markstream CSS.
Use the generic markstream-vue2 skill only when the bundler-specific choice does not matter.
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.md
docs/guide/vue2-installation.md
docs/guide/tailwind.md
docs/guide/troubleshooting.md

이 저장소의 다른 Skills

같은 저장소

markstream-angular

Simon-He95/markstream-vue

Integrate the alpha markstream-angular package into an Angular 20+ app. Use when Codex needs standalone component imports, signal-based examples, CSS wiring, custom HTML tags or customComponents setup, or optional peer integration in an Angular repository.

2026-07-212.8k

markstream-custom-components

Simon-He95/markstream-vue

Override built-in Markstream node renderers and add trusted custom tags across Vue, React, Svelte, and Angular. Use when Codex needs scoped `setCustomComponents`, renderer-local React `streamingComponents` or `htmlComponents`, Angular/Svelte `customComponents`, Vue app-scoped components, node override keys such as `image`, `code_block`, `mermaid`, or `link`, or nested renderers for tags such as `thinking`.

2026-07-212.8k

markstream-install

Simon-He95/markstream-vue

Install and wire markstream-vue, markstream-react, markstream-vue2, markstream-angular, or markstream-svelte into an existing repository. Use when Codex needs to choose the right package, install the smallest framework-specific peer-dependency set, fix CSS/reset order, choose Vue 3 renderer and code-block modes, decide between `content`, `nodes`, and Vue 3 virtual-scroll coordination, or add a minimal working renderer example.

2026-07-212.8k

markstream-migration

Simon-He95/markstream-vue

Audit and migrate existing Markdown rendering to Markstream. Use when Codex needs to replace another renderer, classify direct vs custom vs plugin-heavy usage, preserve behavior during adoption, migrate custom renderers into scoped Markstream overrides, or decide when `nodes` streaming is worth adopting.

2026-07-212.8k

markstream-nuxt

Simon-He95/markstream-vue

Integrate markstream-vue into a Nuxt 3 or Nuxt 4 app. Use when Codex needs client-only boundaries, SSR-safe setup, browser-only peer gating, worker-aware initialization, renderer `mode` selection, or a safe `MarkdownRender` integration inside pages, components, or Nuxt plugins.

2026-07-212.8k

markstream-react

Simon-He95/markstream-vue

Integrate the beta markstream-react package into a React 18+ or Next app. Use when Codex needs to add the React renderer, choose the root, `next`, or `server` entrypoint, import CSS correctly, choose between `content` and `nodes`, keep client boundaries safe, add renderer-local `streamingComponents` or `htmlComponents`, use parser transforms, or prepare a repo for `react-markdown` migration.

2026-07-212.8k

name	markstream-vue2-vite
description	Integrate markstream-vue2 into a Vue 2 plus Vite app. Use when Codex needs Vite-friendly worker imports, `?worker` or `?worker&inline` setup for Mermaid or KaTeX, modern CSS ordering, or Vue 2 compatibility in a Vite-based repository.

Markstream Vue 2 Vite

Use this skill when the host app is Vue 2 and the bundler is Vite.

Workflow

Confirm the repo is Vue 2 with Vite-based tooling.
Install markstream-vue2 plus only the requested optional peers.
Import markstream-vue2/index.css after resets.
Use Vite worker imports when the repo needs bundled workers.
- markstream-vue2/workers/... ?worker or ?worker&inline patterns are allowed here.
Keep Composition API decisions explicit for Vue 2.6 repos.
- For AI chat or streaming UIs, keep content and use built-in smooth streaming first.
  - smooth-streaming="auto" is the default and activates when typewriter=true or max-live-nodes <= 0.
  - typewriter only controls the blinking cursor and defaults to false.
  - fade controls node enter and streamed-text fade animations and defaults to true.
- Streaming vs recovering history: in chat UIs the same MarkdownRender starts streaming and later switches to history when final=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".
- Move to nodes + final only for worker-preparsed content, shared AST stores, or custom AST control.
- Remember that html-policy now defaults to safe, and Mermaid strict mode is on by default through mermaid-props.
Validate with the smallest useful Vite dev or build command.

Default Decisions

Prefer bundled workers over CDN workers in Vite-based Vue 2 repos.
Keep UnoCSS or Tailwind resets before Markstream CSS.
Use the generic markstream-vue2 skill only when the bundler-specific choice does not matter.
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.md
docs/guide/vue2-installation.md
docs/guide/tailwind.md
docs/guide/troubleshooting.md