markstream-svelte
Integrate the beta markstream-svelte renderer into Svelte 5 or SvelteKit with runes, explicit CSS, smooth streaming, workers, and SSR-safe boundaries.
Profile →npx skills add sickn33/agentic-awesome-skills --skill markstream-svelte --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 Svelte ## Overview Integrate Markstream using Svelte 5 runes and SvelteKit-safe browser boundaries. ## When to Use Use for Svelte 5 or SvelteKit package setup, streaming state, workers, or scoped custom components. Svelte 4 is unsupported. ## 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 Svelte 5 and acceptance of a beta package. 2. Install only requested peers; import package CSS after resets and KaTeX CSS only for math. 3. Start with `<MarkdownRender {content} />` and smooth streaming `auto`. 4. For live chat disable fade and opt into the cursor; on completion set `final`, disable pacing/cursor, and enable fade only if desired. 5. Use `nodes` only for worker-owned parsing or shared AST state. 6. Use `$props()` and callbacks. Configure KaTeX or Mermaid workers only when requested. 7. Prefer renderer-local `customComponents`; use scoped registration only when sharing is intentional. 8. Keep browser-only workers behind SvelteKit client boundaries; validate with `svelte-check`, build, or e2e. ## Example ```svelte <script lang="t
- Overview
- When to Use
- Workflow
- Example
- Limitations
- Security & Safety Notes
What does the markstream-svelte skill do?
Integrate the beta markstream-svelte renderer into Svelte 5 or SvelteKit with runes, explicit CSS, smooth streaming, workers, and SSR-safe boundaries.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill markstream-svelte --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.