ワンクリックで
render-debug
Debug rendering issues by tracing HTML through the full pipeline -- parse, style, layout, paint, PDF
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Debug rendering issues by tracing HTML through the full pipeline -- parse, style, layout, paint, PDF
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Dual-perspective code review — Lead Dev (architecture/correctness) + Dev (implementation/tests). Runs entirely in the main agent for easy follow-up.
Update EggPdf documentation — README, docs/ wiki pages, site/, llms.txt, CLAUDE.md — to reflect current implementation
Implement a new feature following EggPdf's test-first, performance-aware development loop
Render HTML through EggPdf and analyze PDF output for visual correctness issues
Render all WebUI templates through the PDF pipeline and verify output correctness
Run EggPdf benchmarks and analyze performance for specific rendering scenarios
| name | render-debug |
| description | Debug rendering issues by tracing HTML through the full pipeline -- parse, style, layout, paint, PDF |
| disable-model-invocation | true |
| user-invocable | true |
| allowed-tools | Bash, Read, Grep, Glob |
Trace an HTML/CSS rendering issue through the full EggPdf pipeline to find where it goes wrong.
$ARGUMENTS -- the symptom to debug (e.g., "div not centering", "table wider than page", "font looks wrong", "page break in wrong place", "image missing")Identify the pipeline stage most likely causing the issue:
| Symptom | Likely Stage |
|---|---|
| Element missing / wrong structure | HTML Parser |
| Style not applied / wrong style | CSS Parser, Cascade, Selector Engine |
| Wrong position / size | Layout Engine |
| Content on wrong page / bad page break | Fragmentation Engine |
| Missing visual (shadow, border-radius, gradient) | Paint Layer |
| Corrupt PDF / can't open / text not selectable | PDF Backend |
| Image missing / wrong size | Image handling + Resource Resolver |
| Font wrong / tofu characters | Text Engine + Font Resolution |
Read the relevant source code for that pipeline stage.
Trace the input through each stage:
Report findings:
Pipeline trace:
Root cause: {which stage and why} Suggested fix: {what code to change} Test to add: {regression test for this case}
If the issue is in layout, provide the box tree with positions:
BlockBox (0, 0) 595x842
BlockBox (20, 20) 555x30 <-- expected 555x50, height wrong
InlineBox (20, 20) "Hello World"