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.
Profile →npx skills add sickn33/agentic-awesome-skills --skill markstream-react --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Overview
- When to Use
- Workflow
- Example
- Limitations
- Security & Safety Notes
What does the markstream-react skill do?
Integrate the beta markstream-react renderer into React 18+ or Next.js with correct client/server entrypoints, CSS, streaming state, and component overrides.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill markstream-react --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.