How do I install the Streaming HTML skill?

Run npx skillmds@latest add thedaviddias/streaming-html in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Streaming HTML safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Streaming HTML?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Streaming HTML free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Streaming HTML?

thedaviddias (@thedaviddias) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Streaming HTML by thedaviddias — Agent Skill

Name: Streaming HTML
Author: thedaviddias

File contents

Stream HTML to the browser before the full response is ready

Traditional SSR waits for all data fetches to complete before sending a single byte of HTML, which means the browser cannot parse, discover subresources, or render anything until the slowest data query finishes. Streaming decouples the delivery of above-fold content from slow database queries and third-party API calls, dramatically improving perceived performance and LCP.

Quick Reference

Streaming sends HTML in chunks as it is generated instead of waiting for the full response
React renderToPipeableStream and Next.js App Router stream by default when you use Suspense
Place Suspense boundaries around slow data dependencies to flush above-fold HTML immediately
Monitor TTFB in Lighthouse — values above 600ms are a sign that streaming is not being used

Check

Examine this server-side rendering implementation to determine whether HTML is streamed in chunks or buffered until fully generated before sending to the client.

Fix

Refactor the SSR implementation to use renderToPipeableStream with Suspense boundaries around slow data fetches, or use ReadableStream in a Node.js handler, so that above-fold HTML is flushed to the client immediately.

Explain

Explain how streaming HTML improves TTFB and FCP by decoupling the delivery of fast content from slow server-side data dependencies.

Code Review

Review server entry points and page components for renderToString calls, missing Suspense boundaries around data-fetching components, and use of await on slow queries before returning a response.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/performance/streaming-html

---name: streaming-htmldescription: Use when reviewing server-side rendering setup, Next.js App Router pages, or Node.js HTTP handlers to verify that HTML is streamed incrementally rather than buffered until completion.---# Stream HTML to the browser before the full response is readyTraditional SSR waits for all data fetches to complete before sending a single byte of HTML, which means the browser cannot parse, discover subresources, or render anything until the slowest data query finishes. Streaming decouples the delivery of above-fold content from slow database queries and third-party API calls, dramatically improving perceived performance and LCP.## Quick Reference- Streaming sends HTML in chunks as it is generated instead of waiting for the full response- React renderToPipeableStream and Next.js App Router stream by default when you use Suspense- Place Suspense boundaries around slow data dependencies to flush above-fold HTML immediately- Monitor TTFB in Lighthouse — values above 600ms are a sign that streaming is not being used## CheckExamine this server-side rendering implementation to determine whether HTML is streamed in chunks or buffered until fully generated before sending to the client.## FixRefactor the SSR implementation to use renderToPipeableStream with Suspense boundaries around slow data fetches, or use ReadableStream in a Node.js handler, so that above-fold HTML is flushed to the client immediately.## ExplainExplain how streaming HTML improves TTFB and FCP by decoupling the delivery of fast content from slow server-side data dependencies.## Code ReviewReview server entry points and page components for renderToString calls, missing Suspense boundaries around data-fetching components, and use of await on slow queries before returning a response.---For full implementation details, code examples, and framework-specific guidance,see `references/rule.md`.Rule page: https://frontendchecklist.io/en/rules/performance/streaming-html

Frequently asked questions

Streaming HTML