Stream HTML to the browser before the full response is ready

SkillMedia

streaming-html is a skill for AI agents that reviews server-side rendering setup, Next.js App Router pages, and Node.js HTTP handlers. It verifies that HTML is streamed incrementally rather than buffered until completion, so pages can be checked for progressive delivery instead of waiting until fully built.

Use Stream HTML to the browser before the full response is ready in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Stream HTML to the browser before the full response is ready and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Stream HTML to the browser before the full response is ready skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Have the server-side rendering code to review, such as Next.js App Router pages or Node.js HTTP handlers.

Stream HTML to the browser before the full response is readyStart free

What your AI can do with it

  • Review server-side rendering setup for incremental HTML streaming
  • Check Next.js App Router pages for streamed rather than buffered HTML
  • Inspect Node.js HTTP handlers for progressive HTML delivery
  • Verify that HTML is not buffered until completion

Getting started

  1. Have the server-side rendering code to review, such as Next.js App Router pages or Node.js HTTP handlers.
  2. Add the streaming-html skill to the agent's available skills.
  3. Ask the agent to review the relevant pages or handlers for incremental HTML streaming.
  4. Review the agent's findings on whether HTML is streamed or buffered.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/streaming-html/SKILL.md and read by ahel’s review.

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

Signals

GitHub stars
74k
Forks
7k
Last commit
Oct 2026

Questions

When should this skill be used?
Use it 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.
What does the skill check for?
It checks whether web pages stream their HTML progressively instead of waiting until fully built.
Advanced
Item type
skill
Key
streaming-html
Source
github.com/thedaviddias/front-end-checklist