원클릭으로 Manus에서 모든 스킬 실행

시작하기

render-compare

스타5

포크0

업데이트2026년 3월 31일 07:59

Render HTML through EggPdf and analyze PDF output for visual correctness issues

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

eggspot

eggspot/EggPdf

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Render Compare

Render HTML through the EggPdf pipeline and analyze the PDF content stream for rendering issues.

Usage

/render-compare <html or template-name>

If argument is a template name (invoice, report, letter, etc.), use that template. If argument is HTML, render it directly.

Steps

Ensure service is running

curl -s http://localhost:55727/health || (dotnet run --project src/EggPdf.Service -c Release -- --urls http://localhost:55727 & sleep 8)

Render the HTML via the API:

curl -s -X POST http://localhost:55727/api/render \
  -H "Content-Type: application/json" \
  -d '{"html":"THE_HTML"}' -o /tmp/render_compare.pdf

Extract and analyze the content stream:

cat /tmp/render_compare.pdf | sed -n '/^stream$/,/^endstream$/p'

Verify paint order (CRITICAL):
- For each element with a background, the fill operation (re f or h f) MUST appear BEFORE the text (Tj)
- If text appears before its background, it will be invisible (painted under the background)
Verify all text is present:
- Extract all Tj operations and check that expected text strings are in the PDF
- Check for ? characters replacing special chars
Verify layout:
- Check X/Y coordinates of text match expected positions
- Check that no content extends beyond page boundaries (MediaBox)
- Check flex item positioning (items should be side-by-side, not stacked)
Report findings with specific issues and suggested fixes

이 저장소의 다른 Skills

같은 저장소

review

eggspot/EggPdf

Dual-perspective code review — Lead Dev (architecture/correctness) + Dev (implementation/tests). Runs entirely in the main agent for easy follow-up.

2026-04-155

docs

eggspot/EggPdf

Update EggPdf documentation — README, docs/ wiki pages, site/, llms.txt, CLAUDE.md — to reflect current implementation

2026-04-075

feat

eggspot/EggPdf

Implement a new feature following EggPdf's test-first, performance-aware development loop

2026-04-035

test-templates

eggspot/EggPdf

Render all WebUI templates through the PDF pipeline and verify output correctness

2026-03-315

bench

eggspot/EggPdf

Run EggPdf benchmarks and analyze performance for specific rendering scenarios

2026-03-215

fix

eggspot/EggPdf

Fix a bug following the test-first approach -- reproduce with test, then fix, then verify

2026-03-215

name	render-compare
description	Render HTML through EggPdf and analyze PDF output for visual correctness issues
allowed-tools	Bash(dotnet ), Bash(curl ), Bash(cat ), Bash(grep ), Read, Grep, Glob, Agent

Render Compare

Render HTML through the EggPdf pipeline and analyze the PDF content stream for rendering issues.

Usage

/render-compare <html or template-name>

If argument is a template name (invoice, report, letter, etc.), use that template. If argument is HTML, render it directly.

Steps

Ensure service is running

curl -s http://localhost:55727/health || (dotnet run --project src/EggPdf.Service -c Release -- --urls http://localhost:55727 & sleep 8)

Render the HTML via the API:

curl -s -X POST http://localhost:55727/api/render \
  -H "Content-Type: application/json" \
  -d '{"html":"THE_HTML"}' -o /tmp/render_compare.pdf

Extract and analyze the content stream:

cat /tmp/render_compare.pdf | sed -n '/^stream$/,/^endstream$/p'

Verify paint order (CRITICAL):
- For each element with a background, the fill operation (re f or h f) MUST appear BEFORE the text (Tj)
- If text appears before its background, it will be invisible (painted under the background)
Verify all text is present:
- Extract all Tj operations and check that expected text strings are in the PDF
- Check for ? characters replacing special chars
Verify layout:
- Check X/Y coordinates of text match expected positions
- Check that no content extends beyond page boundaries (MediaBox)
- Check flex item positioning (items should be side-by-side, not stacked)
Report findings with specific issues and suggested fixes