blitz-dom-pipeline

Process DOM nodes headlessly with Stylo style resolution and Taffy layout computation.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/hafley66/claude-research --skill blitz-dom-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blitz-dom-pipeline
Source: https://github.com/hafley66/claude-research/tree/main/skills/blitz-dom-pipeline
Command: npx skills add https://github.com/hafley66/claude-research --skill blitz-dom-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blitz DOM provides a headless engine to process DOM nodes by performing style resolution, layout computation, and painting without a windowing backend.

Core Features & Use Cases

Core features include a three-phase pipeline (style, layout, paint), a stylo_taffy bridge for converting CSS values to layout, and dirty-node tracking with incremental updates for efficient re-renders. It also supports headless usage and embeddability in game engines and other environments, with integration hooks for Dioxus native-dom.

Quick Start

Instantiate a BaseDocument, add nodes and styles, then call poll() to resolve style and layout.

Frequently Asked Questions about blitz-dom-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I process DOM style and layout without a GUI or windowing backend?

Headless DOM processing resolves styles with Stylo and computes layouts with Taffy inside a BaseDocument without a windowing backend. This enables style, layout, and paint operations in server-side rendering or testing environments.

Can I compute CSS layouts in a game engine or server-side rendering environment?

Yes, you can compute CSS layouts in a game engine or server-side rendering environment by running a headless DOM pipeline. It uses a stylo_taffy bridge to convert CSS values into layout computations independently of a graphical interface.

How do I resolve styles and compute layouts for DOM nodes step by step?

To resolve styles and compute layouts step by step, instantiate a BaseDocument, add your nodes and styles, then call poll(). This triggers the three-phase pipeline to execute STYLE, LAYOUT, and PAINT operations sequentially.

Does headless DOM processing support incremental updates for efficient re-renders?

Headless DOM processing supports incremental updates for efficient re-renders by using dirty-node tracking. This mechanism ensures that only modified nodes are processed during the style and layout phases, avoiding full document recalculations.

Can I use Dioxus native-dom integration with a headless layout and paint pipeline?

Yes, you can use Dioxus native-dom integration with a headless layout and paint pipeline. The engine provides specific integration hooks that allow Dioxus to interface directly with the headless DOM processing architecture.