メニュー
Capture screenshots of all manual pages at high resolution for translation verification. Use when verifying that translations match page images, checking layout correctness, or inspecting for content mismatches.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Takazudo/takazudomodular-manuals --skill l-capture-all-pagesコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| name | l-capture-all-pages |
| description | Capture screenshots of all manual pages at high resolution for translation verification. Use when verifying that translations match page images, checking layout correctness, or inspecting for content mismatches. |
Capture all pages of the manual viewer at high resolution (2000x1600) for visual verification of translations.
This skill captures screenshots of all pages in the manual viewer to verify that:
Prerequisites:
pnpm dev)Usage:
# Capture all pages (default: 30 pages)
node .claude/skills/capture-all-pages/scripts/capture.js
# Capture specific number of pages
node .claude/skills/capture-all-pages/scripts/capture.js --pages 280
# Custom base URL
node .claude/skills/capture-all-pages/scripts/capture.js --base-url http://zmanuals.localhost:3300/oxi-one-mk2/page
The capture script supports these options:
--pages <number> - Total pages to capture (default: 30)--base-url <url> - Base URL for pages (default: http://zmanuals.localhost:3300/oxi-one-mk2/page)--output-dir <path> - Custom output directory (default: __inbox/captures-{timestamp})Default settings:
__inbox/captures-{YYYYMMDD}-{HHMMSS}/page-001.png to page-NNN.pngVerify dev server is running
curl -s -o /dev/null -w "%{http_code}" http://zmanuals.localhost:3300/oxi-one-mk2/page/1
# Should return 200
Run capture script
node .claude/skills/capture-all-pages/scripts/capture.js
The script will:
Check results
ls -lh __inbox/captures-*/page-*.png
__inbox/captures-20260103-163245/
├── page-001.png (2000x1600)
├── page-002.png (2000x1600)
├── page-003.png (2000x1600)
...
├── page-030.png (2000x1600)
└── summary.json (capture results)
summary.json contains:
__inbox/ directory (gitignored)Verify committed manual PDFs against the revision each manufacturer currently publishes, and propose (or run) refreshes for stale ones. Use when: (1) User says 'check stale manuals', 'verify manuals', 'manual sweep', 'staleness check', or asks whether any manual is outdated, (2) A manufacturer ships new firmware or a new manual revision for a product we host, (3) A periodic re-verification is due (manuals silently drift — a stale one looks healthy from inside the repo), (4) Before relying on a manual's content for other work and freshness matters. Covers per-brand source URLs, download etiquette, hash/content triage, and the reprocess flows.
Run the complete PDF processing pipeline to convert the manual PDF into Next.js application data. This command executes all steps automatically: split, render, extract, translate, build, and manifest.
Run comprehensive pre-push validation covering code quality, build, production server, and smoke e2e tests. Use when: (1) Completing a PR or feature implementation, (2) Before pushing significant changes, (3) After large refactors, (4) User says 'b4push', 'before push', 'check everything', or 'ready to push'.