ChatGPT Claude Codex CLI Cohere Cursor DeepSeek Gemini GitHub Copilot GLM Grok Kimi Llama MiniMax Mistral OpenAI opencode Skill

markstream-react

Integrate the beta markstream-react renderer into React 18+ or Next.js with correct client/server entrypoints, CSS, streaming state, and component overrides.

LLM Mart · 0 points · 21 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download sickn33-agentic-awesome-skills-skills_markstream-react-286166a.zip · 1 KB
Part of sickn33/agentic-awesome-skills — 427 skills
This skill couldn't be refreshed from GitHub on the last check — you're seeing the last imported snapshot.

Install

skills CLI npx skills add https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/markstream-react
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install sickn33-agentic-awesome-skills@llmmart
Git git clone https://github.com/sickn33/agentic-awesome-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole sickn33/agentic-awesome-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Markstream React

Overview

Wire the beta React renderer into React 18+ or Next.js without crossing client/server boundaries or reaching for AST control unnecessarily.

When to Use

Use for React/Next setup, root/next/server entrypoints, streaming, component overrides, or migration support. Pair with markstream-migration for renderer replacement.

Workflow

Before changing dependencies or source files, inspect the existing package manager and project conventions, preview the intended edits, and obtain explicit user approval.

  1. Confirm React 18+ and acceptance of a beta package.
  2. Install only requested peers and import markstream-react/index.css.
  3. Use the root entry for client rendering, /next for Next-specific components, and /server for server rendering without client hooks.
  4. Start with content and smoothStreaming="auto"; use nodes plus final only when another layer owns parsing.
  5. For live chat disable fade and opt into the cursor. On completion set final, disable pacing/cursor, and enable fade only if desired.
  6. Keep browser-only peers inside 'use client', dynamic ssr: false, or another minimal boundary.
  7. Prefer streamingComponents for parser-backed tags and htmlComponents for sanitized props. Use scoped registry overrides for built-in nodes.
  8. Keep htmlPolicy="safe" and Mermaid strict; validate client, server, and incremental paths.

Example

import MarkdownRender from 'markstream-react'
import 'markstream-react/index.css'

export function StreamingAnswer({
  content,
  isDone,
}: {
  content: string
  isDone: boolean
}) {
  return (
    <MarkdownRender
      content={content}
      final={isDone}
      fade={isDone}
      typewriter={!isDone}
      smoothStreaming={isDone ? false : 'auto'}
      htmlPolicy="safe"
    />
  )
}

Limitations

  • The package is beta and requires React 18+.
  • Browser-only peers require client boundaries under SSR.
  • Complex parser parity requires separate migration review.

Security & Safety Notes

Review dependencies and never opt untrusted model output into trusted HTML or loose diagram rendering.

Files (agentic-awesome-skills)
  • SKILL.md 2.7 KB
    ---
    name: markstream-react
    description: "Integrate the beta markstream-react renderer into React 18+ or Next.js with correct client/server entrypoints, CSS, streaming state, and component overrides."
    category: frontend
    risk: critical
    source: https://github.com/Simon-He95/markstream-vue/tree/main/.agents/skills/markstream-react
    source_repo: Simon-He95/markstream-vue
    source_type: official
    date_added: "2026-07-21"
    author: Simon-He95
    tags: [react, nextjs, markdown, streaming, ssr]
    tools: [claude, cursor, gemini, codex]
    license: MIT
    license_source: https://github.com/Simon-He95/markstream-vue/blob/main/license
    ---
    
    # Markstream React
    
    ## Overview
    
    Wire the beta React renderer into React 18+ or Next.js without crossing client/server boundaries or reaching for AST control unnecessarily.
    
    ## When to Use
    
    Use for React/Next setup, root/`next`/`server` entrypoints, streaming, component overrides, or migration support. Pair with `markstream-migration` for renderer replacement.
    
    ## Workflow
    
    Before changing dependencies or source files, inspect the existing package manager and project conventions, preview the intended edits, and obtain explicit user approval.
    
    1. Confirm React 18+ and acceptance of a beta package.
    2. Install only requested peers and import `markstream-react/index.css`.
    3. Use the root entry for client rendering, `/next` for Next-specific components, and `/server` for server rendering without client hooks.
    4. Start with `content` and `smoothStreaming="auto"`; use `nodes` plus `final` only when another layer owns parsing.
    5. For live chat disable fade and opt into the cursor. On completion set `final`, disable pacing/cursor, and enable fade only if desired.
    6. Keep browser-only peers inside `'use client'`, dynamic `ssr: false`, or another minimal boundary.
    7. Prefer `streamingComponents` for parser-backed tags and `htmlComponents` for sanitized props. Use scoped registry overrides for built-in nodes.
    8. Keep `htmlPolicy="safe"` and Mermaid strict; validate client, server, and incremental paths.
    
    ## Example
    
    ```tsx
    import MarkdownRender from 'markstream-react'
    import 'markstream-react/index.css'
    
    export function StreamingAnswer({
      content,
      isDone,
    }: {
      content: string
      isDone: boolean
    }) {
      return (
        <MarkdownRender
          content={content}
          final={isDone}
          fade={isDone}
          typewriter={!isDone}
          smoothStreaming={isDone ? false : 'auto'}
          htmlPolicy="safe"
        />
      )
    }
    ```
    
    ## Limitations
    
    - The package is beta and requires React 18+.
    - Browser-only peers require client boundaries under SSR.
    - Complex parser parity requires separate migration review.
    
    ## Security & Safety Notes
    
    Review dependencies and never opt untrusted model output into trusted HTML or loose diagram rendering.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related