Gog Pamphlet

GOG backup pamphlet

The user prints a small pamphlet for each personal backup disc, styled as a modern reissue line. This skill turns a GOG store URL into finished print panels.

This is cosmetic dressing meant to make a shelf of burned discs look like a real product line. Don't agonise over near-equivalent legal entities or hedge every uncertainty — pick the most defensible option and say so in one line. But facts that get printed should be true: dates, ratings, DLC and company names are worth a minute of checking, because a wrong one is permanent once it's in the case.

Related: gog-case-insert covers the case artwork metadata. This skill reuses its QR script. Don't duplicate its job.

What gets built

Two cards, four panels, each 483 × 629 (127.79 × 166.42 mm at 96 dpi):

Health & safety, warranty and "also available" are not per-title — the user has a separate stock print for those. Never add them here.

The flow

1. Locate the folder — never duplicate

Search the pipeline before creating anything:

find . -ipath '*<title>*' -not -path '*/.*' | sort

Titles live in 0.1_Games in Progress/, 0.2_Ready for Print/, 0.4_Printed/ or 0.5_Archive/. If one already exists anywhere, work in it — many of these discs are already printed and the case insert is done. Only create 0.1_Games in Progress/<Title>/{Assets,For Print} for a genuinely new title.

Output goes to <title folder>/Pamphlet/, and build_set.py makes SVG/ and PNG/ inside it.

2. Scrape the store page

Open the URL in the browser, then wait and scroll before reading page text — the preservation badge, changelog and HowLongToBeat figures lazy-load and read as absent if you query straight after navigating. This has caused a wrong answer before.

navigate → wait 3s → scroll down 14 → wait 2-3s → javascript_exec

From window.productcardData.cardProduct take: id, title, publishers, developers, globalReleaseDate, gogReleaseDate, copyrights, esrbRating, pegiRating, features, size, localizations, supportedOperatingSystems, bonuses, and cardProductDlcs.

From document.body.innerText take: the preservation marker, "What improvements we made" changelog, "Time to beat", "Genre:/Tags:", and critic/user scores.

Keep each extraction under ~2,500 characters or it truncates mid-object. For a batch, chain several navigate → wait → scroll → js groups in one browser_batch call.

3. Decide preserved or not — this gates card B

A title is in the GOG Preservation Program when the page text contains "We made this game up to today's standards as part of GOG Preservation Program" (usually alongside "This game is 2026-ready" and "Windows 11 verified").

Test /GOG Preservation Program/i against the rendered text.

The "Good Old Game" tag is not the signal. Mad Max carries it; FFIX, Breath of Fire IV and both Witchers are all in the programme and none of them do. Going by the tag would have silently dropped card B from four titles.

Set "preserved": true|false in card2.json. A non-preserved build emits card A only and deletes any stale BF/BB from a previous run.

4. QR badge

Reuse the case-insert script. It needs the qrcode package, so make a venv in the scratchpad if there isn't one:

python3 -m venv "$SP/venv" && "$SP/venv/bin/pip" -q install qrcode
"$SP/venv/bin/python" .claude/skills/gog-case-insert/scripts/generate_qr_badge.py \
  "<canonical url>" "<gog id>" "<Title folder>/Assets/<Title>_qr.svg" 31 45

Check for an existing QR first. Some titles carry an older bare-QR style with no ID header — regenerate as a badge and keep the old one as *_qr_old_bareQR.svg.

5. Logos

Check 0.3_Assets/Logos/Publishers-Developers/ before anything else — most major studios are covered. Ask before downloading any logo, naming the file, source and format. Say plainly when a defunct studio has no findable mark rather than inventing one. SVG and PNG/JPEG both work.

6. Publisher address

GOG has no address field. Look up the current registered or business address of the entity that actually holds the rights, and cite where it came from. Companies House, the French company registry, and a publisher's own imprint/legal-notice page are all good sources.

7. Production history — preserved titles only

Card B's back needs a real research pass: studio, engine, development story, release dates by region, what changed in later editions, reception, credits. Verify against Wikipedia or primary sources rather than recall — a plausible-sounding date that turns out wrong is worse than omitting it. Write 3 paragraphs, a dated timeline, a reception line and a credits line.