# Latent Space Thumbnail Director

> Create, revise, or review Latent Space and Forward Deployed Engineering YouTube thumbnails using saved brand resources, curiosity-led editorial preferences, cast and company coverage rules, timestamp-safe layout, and approved examples. Use for Latent Space or FDE episode thumbnails, not unrelated channels.

- Skill: `swyxio/latent-space-thumbnail-director` (Agent Skill, multi-file: 14 files)
- Install (CLI): `npx skillmds@latest add swyxio/latent-space-thumbnail-director`
- Raw SKILL.md: https://api.skillmd.com/api/skills/swyxio/latent-space-thumbnail-director/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: swyxio (https://skillmd.com/u/swyxio)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/swyxio/latent-space-thumbnail-director

---


# Latent Space Thumbnail Director

Direct and QA Latent Space and FDE thumbnails. Use `$imagegen` for raster generation or editing. When the user selects `$artifact-template-latent-space-fde-thumbnail`, use that template as the visual starting point and this skill as the learned editorial and production layer.

## Load the relevant guidance

- Read [references/preferences.md](references/preferences.md) for every creation, revision, or review.
- Read [references/resource-index.md](references/resource-index.md) when locating logos, identity references, source pages, or font assets.
- Read [references/example-index.md](references/example-index.md) when choosing an art direction, producing variants, or comparing a result with approved work.

## Workflow

1. Ground the episode from the user's brief and supplied sources. Extract specific tensions, decisions, consequences, or counterintuitive claims; do not invent episode facts.
2. Choose one curiosity hook, normally two to six words. Use one headline and at most one supporting visual metaphor.
3. Build an explicit coverage list before generation: every requested person exactly once, every participating company exactly once, and no unrequested host.
4. Use the official Latent Space logo asset and supplied identity or company references. Do not recreate an unavailable identity or wordmark from memory.
5. Generate a 16:9 master with one dominant idea, one hero region, and strong mobile hierarchy. Multiple directions must vary the hook and composition, not merely color.
6. Inspect the result at full size and at approximately 320 x 180. Verify headline spelling, count people and companies, check facial fidelity, wardrobe separation, LS x FDE branding, and the bottom-right duration-overlay exclusion zone.
7. Repair material defects before delivery. Export a high-resolution master and an upload-ready 1280 x 720 JPG.

## Non-negotiables

- Keep the bottom-right duration-overlay zone free of essential content. DAILY belongs before that zone, not at the extreme right edge.
- Do not let several dark shirts merge into the near-black background. Relight or recolor clothing while preserving faces and identity.
- Keep the official LS hex compact in the upper-right with `FDE`; prefer Tachyon only when an actual Tachyon font file is available.
- Preserve complete guest and company coverage. A sparse composition is not permission to drop people or logos.
- Avoid biographies, dates, paragraph copy, ornamental UI, screenshots, duplicate faces, and tiny badges unless the user specifically requests them.