Case study / Claude Code build
A quality watcher for a growing comics catalog
A digital comics publisher wanted every new release checked before readers found the problems. We built a read-only watcher with Claude Code. It finds what changed, checks it in a real browser and hands the content team a ready-to-fix backlog.
Digital comics publisher with a multilingual catalogue
A read-only quality watcher, built with Claude Code
Recurring cross-checks, recorded in the team’s tracker
System blueprint
The whole system on one sheet
Select any block to see what it does, or open it full screen and watch the system run from signal to action.
The problem
Manual checks could not keep pace
New episodes go live regularly in several languages. Checking each one by hand was slow and could not be repeated on every release. The person collecting issues could not edit the site; fixes belonged to a senior manager.
How it works
Four steps on every run
- 01 / Detect
Find what changed
Compares the sitemaps and homepage shelves with the last run to list new and changed series and episodes.
- 02 / Check
Read it like a reader
Opens each new episode in a real browser on desktop and mobile and checks what a reader would notice.
- 03 / Ticket
Grade every finding
Turns each problem into a ticket: severity P0 to P2, the URL, evidence and a suggested fix.
- 04 / Re-check
Close the loop
The team fixes from its tracker. The next run re-checks and flags anything that comes back.
What each run checks
What a careful reader would notice
New releases are checked in depth. A rotating sweep covers the rest of the catalogue over time: status codes, broken links, duplicate titles and page errors.
Publishing
Page loads, every panel image appears in order, navigation and lock state are right.
Visual
No stretched or cut-off panels, and no sideways scrolling in the mobile reader.
Content
Titles, synopses and tags checked for typos, placeholders and untranslated text.
Search and sharing
Titles, canonical links, language alternates, structured data and share images.
What the team receives
Every finding arrives ready to fix
Each ticket says how serious the problem is, where it is, how to see it and what to change. Issues keep their first-seen and last-seen dates, so a problem that returns is marked as a regression.
Untranslated synopsis on a new episode
- Page
- /series/example/episode-12 (one language version)
- Steps
- Open the episode in that language version.
- Expected
- Synopsis in the page language.
- Actual
- Synopsis shown in English.
- Evidence
- Screenshot and page text attached.
- Fix
- Add the translated synopsis in the CMS.
What the team reported
Checks the team can repeat on every release
The publisher’s content team uses the watcher as an internal tool. Issues are recorded in the team’s tracker, checking is easier and faster than reviewing pages by hand, and a recurring cross-check is now possible. The team uses it to improve reader experience and content quality.
Outcomes as reported by the publisher’s team. Issue counts and time saved are not published. For a new build, record the release volume, current review time and issue baseline first.
Edits made to the live site by the watcher. It reads, checks and reports; people decide and fix.
Contribution and scope
Who did what
AGI Technologies designed the checks, severity rules and ticket format, and built the watcher with Claude Code. It runs in a real browser session with reader-level access. The publisher’s team reviews the backlog, sets priorities and makes every fix.
Apply it to your site
Put a quality check on every release
If your team publishes often and checks pages by hand, we can define the checks, guardrails and hand-off for a first watcher.