Agent skill · software engineering · aiskillstore
markstream-nuxt
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.
Why this skill is useful
Provides specific integration patterns and SSR-safe setup instructions for using markstream-vue with Nuxt applications that the AI wouldn't reliably generate on its own.
What it needs
Requires markstream-vue installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Markstream Nuxt Use this skill when the host app is Nuxt and SSR boundaries matter. Workflow 1. Confirm the repo is Nuxt 3 or 4. 2. Install markstream-vue plus only the optional peers required by the requested features. 3. Keep browser-only peers behind client-only boundaries. Prefer <client-only> wrappers, .client plugins, or guarded setup paths. 4. Import markstream-vue/index.css from a client-safe app shell or plugin. The root JS import does not inject styles; use markstream-vue/index.css or markstream-vue/index.px.css explicitly. 5. Start with content, choose the renderer mode by surface, and move to nodes plus final only when the UI needs custom AST control. Use mode="chat" for AI chat or SSE output. It uses lightweight batches, <pre> code rendering by default, fade=false, and max-live-nodes=0; smooth-streaming="auto" paces visible output. Use mode="docs" for rich document surfaces. It is the default, enables larger batches, tooltips, fade, and Monaco-backed code blocks when the peer is installed. Use mode="minimal" for lightweight non-chat surfaces. typewriter only controls the blinking cursor and defaults to false. When overriding mode defaults on a high-frequency stream, pair smooth streaming with :fade="false" to avoid delta fade stacking with high-commit pacing. Streaming vs recovering history: in chat UIs the same MarkdownRender starts streaming and later switches to history when final=true. Streaming: mode="chat", smooth-streaming="auto", :fade="false", typewriter=true. Recovering/completed chat history: keep mode="chat" on the same chat row; use :smooth-streaming="false", typewriter=false, and only set :fade="true" when the host explicitly wants a history-entry animation. Use mode="minimal" for lightweight non-chat recovered content, and use mode="docs" only for rich document surfaces. In SSR, avoid smooth-streaming="true" on first-screen content; the mounted gate inside auto prevents hydration mismatch. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/markstream-nuxt