Open Design Landing Deck
OpenDesign's brand-story deck for partners and press: why it exists, what it believes, and where design is going. Built as a decision-grade marketing & GTM deck for partners, press, community.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Open Design Landing Deck when an AI agent needs a reusable SKILL.md workflow for this job: OpenDesign's brand-story deck for partners and press: why it exists, what it believes, and where design is going. Built as a decision-grade marketing & GTM deck for partners, press, community.
When not to use it
Skip Open Design Landing Deck when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/open-design-landing-deck # Save SKILL.md to ~/.claude/skills/open-design-landing-deck/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/open-design-landing-deck/SKILL.md. For a shared project, commit the folder at .claude/skills/open-design-landing-deck/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Open Design Landing Deck skill for this task: Use Open Design Landing Deck when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# open-design-landing-deck
Sister skill to [`open-design-landing`](../open-design-landing/). Same Atelier Zero visual system (warm paper, Inter Tight + Playfair Display, italic-serif emphasis, coral dots), but paginated as a **horizontal magazine-style swipe deck** instead of a long scrolling page.
The navigation model is intentionally borrowed from the [`guizang-ppt`](../guizang-ppt/) skill — `←/→` arrow keys, wheel / swipe, ESC for the overview grid — so it feels like a print magazine flipping page by page rather than a web slide deck scrolling.
```text inputs.json + ../open-design-landing/styles.css │ └──────────► scripts/compose.ts │ ▼ <out>/index.html (one viewport per slide, horizontal swipe) ```
## What you get
- A single self-contained HTML file with N viewport-sized slides laid out horizontally on one transformed flex track. - **Keyboard navigation**: `←/→` · `↑/↓` · PageUp/PageDown · Space · Home/End. - **Wheel + touch swipe** (with momentum guard so a single trackpad flick doesn't overshoot). - **Per-slide chrome strip**: brand mark, deck title, location, Roman-numeral year, live slide counter (`01 / 11`). - **Coral progress bar** at the bottom that fills as you advance. - **Dot indicator** strip near the bottom; click any dot to jump. - **ESC overview grid** — scaled thumbnails of every slide, click to jump. Mirrors `guizang-ppt`'s overview UX. - Reuses the **same 16-slot image library** as the sister skill — no duplicate assets.
## Slide types
| Kind | Use it for | | :---------- | :------------------------------------------------------------ | | `cover` | Title plate at the start. 2-column copy + collage art. | | `section` | Roman-numeral divider between chapters. Centered, full-bleed. | | `content` | Eyebrow + title + body + bullets + optional collage art. | | `stats` | Up to 4 large stat cells (value · label · sub-label). | | `quote` | Pull quote + author. Optional portrait collage on the right. | | `cta` | Closing pitch + 1-2 buttons. | | `end` | Mega italic-serif kicker word + signature footer. |
A typical 11-slide pitch:
``` 1. cover — title plate, hero collage 2. section — "I. The problem" 3. content — about / manifesto, bullets 4. content — capabilities, bullets 5. stats — 4 numbers 6. section — "II. How it feels" 7. content — method, bullets 8. content — selected work 9. quote — customer testimonial 10. cta — primary + secondary action 11. end — mega kicker + signature ```
## Workflow
### 1. Author `inputs.json`
Start from [`inputs.example.json`](./inputs.example.json) (the Open Design pitch deck). The brand block, image strategy, and assets path mirror the sister skill — if you already filled out an `open-design-landing` brief, copy `brand` and `imagery` over verbatim.
For each slide, pick a `kind` and fill the typed fields from [`schema.ts`](./schema.ts). `MixedText` (sans-serif baseline + italic-serif emphasis spans + coral terminating dot) is the same encoding used by the sister skill — see its `inputs.example.json`.
### 2. (Optional) generate or stub imagery
This skill does **not** ship its own image generator or placeholder script — it shares the 16-slot library from `open-design-landing`. To regenerate or stub:
```bash # generate via gpt-image-2 (fal.ai) FAL_KEY=... npx tsx ../open-design-landing/scripts/imagegen.ts ../open-design-landing/inputs.example.json --out=../open-design-landing/assets/
# or paper-textured SVG placeholders npx tsx ../open-design-landing/scripts/placeholder.ts ../open-design-landing/assets/ ```
Set your deck's `inputs.imagery.assets_path` to wherever those PNGs live (default in the example: `../open-design-landing/assets/`).
### 3. Compose the deck
```bash npx tsx scripts/compose.ts inputs.json out/index.html ```
The composer reads `inputs.json`, loads the canonical Atelier Zero stylesheet from `../open-design-landing/styles.css`, layers deck-specific rules on top (horizontal flex track, slide layouts, HUD, dot nav, ESC overview, keyboard / wheel / touch handlers), and writes one self-contained HTML file.
### 4. Self-check
- [ ] Open the HTML in a fresh browser tab; slide 1 (cover) shows with chrome strip top-right showing `01 / N`. - [ ] Press `→` (or Space, or scroll-down). Smoothly slides one viewport to the right; dot nav advances; the coral progress bar ticks forward. - [ ] Press `End`. Jumps to the final slide. - [ ] Press `Home`. Returns to slide 1. - [ ] Press `Esc`. Overview grid appears with scaled thumbnails; click any tile to jump and dismiss the overview. - [ ] Resize to 1080px and 640px. Cover / content slides collapse to a single column; dot nav still works; chrome strips shrink. - [ ] `prefers-reduced-motion: reduce` (DevTools → Rendering): page transitions stay snappy and don't induce motion sickness. - [ ] Lighthouse: contrast AA, font-display swap, no layout shift.
## Boundaries
- **Reuse the sister skill's stylesheet.** The composer reads `../open-design-landing/styles.css` at compile time. Do not maintain a duplicate copy here; if Atelier Zero tokens evolve, edit them once in the sister skill. - **Reuse the sister skill's image library.** No need to re-prompt or re-render — the same 16 plates work for both surfaces. - **Keep slides single-viewport.** If a slide's content does not fit 100vh × 100vw at 1280×800 it will overflow and feel cramped. Trim copy or split into two slides. - **Do not switch to vertical scroll-snap.** The horizontal swipe posture is what makes this skill feel like a magazine spread; a vertical scroller would just be a long landing page. - **Do not add a router.** This is a single-file artifact. Multi-page decks are out of scope; for a multi-deck experience, render each deck separately and link from a parent index.
## See also
- [`open-design-landing`](../open-design-landing/) — landing page sister skill. - [`guizang-ppt`](../guizang-ppt/) — the magazine-deck navigation pattern this skill borrows. - [`design-systems/atelier-zero/DESIGN.md`](../../design-systems/atelier-zero/DESIGN.md) — token spec.
Intended uses
- Use Open Design Landing Deck when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.