template-forgelisted

*[日本語](SKILL.ja.md)* # Template Forge — Create a New Slide Template (Master) ## Important - **The Slides API cannot create or rename masters/layouts** (`references/api-notes.md` §1). This skill therefore *derives*: it copies a base and restyles the base's existing layout pages. Unused base layouts remain in the file — unregistered and harmless. Role names live only in `templates/<id>.json`'s alias table. - **The base's colorScheme is immutable** — every color is written as explicit RGB. The Slides UI color picker will still show the base's theme palette; that is expected (same as `templates/corporate.json`). - **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`). - **Never hand the template over without visual verification.** Role assignment is deterministic, but band/placeholder overlap, font rendering, and contrast are judged only by eye: always run the layout catalog + the `slide-qa` skill (Phase 5) before reporting done. - **Fixes happen in the design spec.** On any defect, edit the spec and rebuild with `--replace` (deletes the superseded master from Drive after a successful rebuild). Never patch the generated master in the Slides UI — that forks it from the spec. - **Fonts must exist in the Slides font menu** (Google Fonts). Unknown names fall back silently. Known-s