Menu
Use `chromium --dump-dom` to inspect the fully rendered DOM after JavaScript execution. For debugging layout/scrolling issues and scraping dynamic pages.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
C# 14 coding standards. Invoke this skill always when working in C# language.
Rust coding standards for production code. Invoke this skill always when working in Rust language.
Expert guide for writing git commit messages following the Conventional Commits 1.0.0 specification.
Multi-repository codebase exploration. Research library internals, find code patterns, understand architecture, compare implementations across GitHub/npm/PyPI/crates. Use when needing deep understanding of how libraries work, finding implementations across open source, or exploring remote repository structure.
Best practices for writing clean, maintainable, and robust tests with TUnit.
| name | dump-dom |
| description | Use `chromium --dump-dom` to inspect the fully rendered DOM after JavaScript execution. For debugging layout/scrolling issues and scraping dynamic pages. |
Get the actual browser-rendered DOM after JS runs. Unlike static HTML, this shows hydrated content, dynamic elements, and runtime changes.
chromium --headless --no-sandbox --disable-gpu --virtual-time-budget=8000 --dump-dom <url>
curl cannot captureIf a div won't scroll, seeing the real DOM (nesting, styles, attributes) is faster than tracing through JSX components.
--virtual-time-budget if DOM is incomplete