slide-qalisted
Install: claude install-skill wfukatsu/slide-forge
*[日本語](SKILL.ja.md)*
# Visual QA for Generated Slides (thumbnail-based)
Follow the QA scope in `references/workflow-contract.md`. The first pass is a
complete visual inspection; repair passes are impact-scoped.
## Important
- **Scope**: post-generation visual verification only. The offline coordinate
gate (Gate 1: `build_deck.py --dry-run` / `validate_layout.py`) belongs to
the generation skills and runs **before** generation; this skill is Gate 2
(`references/validation.md` has the full two-gate rationale).
- **Run every command from the slide-forge root as cwd** — `${CLAUDE_PLUGIN_ROOT}`
when running from an installed plugin, `/path/to/slide-forge` on a
local clone. Auth and the venv are shared at the repo root (`config/`, `.venv`).
- **Whether to run QA is settled at generation time.** The generation skills ask
during intake (default: **run** — recommend it; a clean API response cannot
show overflowing text or a misattached arrow). When the user skipped QA, the
generation skill says so in its report and offers this skill as a follow-up.
- **Fixes happen in the source, not the artifact.** On any defect, fix the spec
/ deck module in the originating skill's flow and regenerate. Never patch a
generated deck in place.
- **Always clean up when done.** The thumbnails exist only for this
verification and are re-fetchable at any time. Delete them with
`scripts/cleanup_qa.py` before reporting — even when QA is aborted midway.
Superseded decks created d