Skip to content
Back to search

future-slide-skill

The workflow for disciplined slide generation. Extract design, plan the deck, render with consistency.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/bytonylee--future-slide-skill/badge.svg)](/listings/bytonylee--future-slide-skill)

HTML

<a href="/listings/bytonylee--future-slide-skill"><img src="/api/listings/bytonylee--future-slide-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install with `npx skills`

Use the Skills CLI from a terminal with Node.js 18+:

npx skills add jyoung105/future-slide-skill

You can also use the repository URL:

npx skills add https://github.com/jyoung105/future-slide-skill.git

Restart Codex after installation so the new skills are discovered.

Manual install into `.codex`

Download or clone this repository, then copy the skill folders into your Codex skills directory:

mkdir -p ~/.codex/skills
cp -R skills/slide-design ~/.codex/skills/
cp -R skills/gpt-image-slide ~/.codex/skills/
cp -R skills/gpt-image-slide-plan ~/.codex/skills/
cp -R skills/gpt-image-slide-prompt ~/.codex/skills/
cp -R skills/gpt-image-slide-render ~/.codex/skills/
cp -R skills/tightened-slide ~/.codex/skills/

For project-local installation, copy the same folders into:

.codex/skills/

Codex discovers skills from folders that contain `SKILL.md`, so each copied folder must keep its `SKILL.md` at the folder root.

[Back to top](#future-slide-skill)

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 353 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Future Slide Skill
  2. [English](./README.md) | [한국어](./README.ko.md)
  3. ![Version](https://img.shields.io/badge/version-v0.0.3-333333?style=flat-square)
  4. [![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-yellow.svg)](./LICENSE)
  5. Navigation: [Workflow](#recommended-workflow) |
  6. [Tightened Slide](#tightened-slide-html-decks) |
  7. [Examples](#example-prompts) | [Install](#installation) | [License](#license)
  8. ![Future Slide Skill Flow](public/diagram/four-skill-flow.png)
  9. A reusable skill bundle for turning:
  10. 1. a **reference slide image**
  11. 2. **user-provided files**
  12. 3. a **user prompt / deck request**
  13. into a disciplined four-stage slide-generation workflow:
  14. 1. **Extract `DESIGN.md` from the reference slide image**
  15. 2. **Build a persuasive slide plan in JSON**
  16. 3. **Write page-by-page slide prompts in JSON**
  17. 4. **Generate page images sequentially from the prompt JSON**
  18. This bundle is intentionally modeled after the *reason* `gpt-taste` exists in the `taste-skill` repo: not to add more decoration, but to add **stricter enforcement**, stronger anti-default rules, and mandatory pre-flight structure so GPT-class models do not skip steps or collapse into generic output.
  19. ## Why this is split into 4 skills
  20. A single prompt often fails in predictable ways:
  21. - it starts writing slides before the theme is extracted
  22. - it mixes design analysis with deck strategy
  23. - it produces page prompts without a real narrative arc
  24. - it loses layout consistency across body slides
  25. - it overfits to the visible text in the reference image instead of the slide *design system*
  26. - it stops after writing prompts and never actually renders numbered slide outputs
  27. So this bundle separates responsibilities:
  28. - **`slide-design`** → extract a reusable `DESIGN.md`
  29. - **`gpt-image-slide-plan`** → decide deck logic, ordering, and persuasion
  30. - **`gpt-image-slide-prompt`** → convert that plan into detailed page prompts
  31. - **`gpt-image-slide-render`** → generate slide images sequentially and save them with page-number filenames
  32. ## New command families
  33. Use the newer command families when you want to choose the output mode explicitly.
  34. ### GPT image slide commands
  35. - **`$gpt-image-slide`** → run the full image workflow: design → plan → prompt → render
  36. - **`$slide-design`** → only create `DESIGN.md`
  37. - **`$gpt-image-slide-plan`** → only create `slide_plan.json`
  38. - **`$gpt-image-slide-prompt`** → only create `slide_prompts.json`
  39. - **`$gpt-image-slide-render`** → only render `page_1.png ... page_N.png`
  40. ### HTML slide commands
  41. - **`$html-slide`** → run the full HTML workflow: design → plan → prompt → render
  42. - **`$slide-design`** → only create browser-implementable `DESIGN.md`
  43. - **`$html-slide-plan`** → only create `slide_plan.json`
  44. - **`$html-slide-prompt`** → only create `html_slide_prompts.json`
  45. - **`$html-slide-render`** → only build the HTML slide deck
  46. ### Tightened Slide command
  47. - **`$tightened-slide`** → build a single-file HTML horizontal-swipe deck with locked layouts, strict grid rules, image-slot discipline, and validation
  48. ## Recommended workflow
  49. Use the skills in this exact sequence:
  50. ### 1) `slide-design`
  51. Inputs:
  52. - reference slide image(s)
  53. Output:
  54. - one `DESIGN.md` focused on presentation design, not slide content
  55. ### 2) `gpt-image-slide-plan`
  56. Inputs:
  57. - extracted `DESIGN.md`
  58. - user files
  59. - user goal / audience / prompt
  60. Output:
  61. - deck plan JSON with slide ordering, narrative flow, and evidence mapping
  62. ### 3) `gpt-image-slide-prompt`
  63. Inputs:
  64. - `DESIGN.md`
  65. - plan JSON
  66. - supporting files if needed
  67. Output:
  68. - slide-by-slide prompt JSON with detailed visual/content instructions
  69. ### 4) `gpt-image-slide-render`
  70. Inputs:
  71. - `DESIGN.md`
  72. - page-level prompt JSON such as `slide_prompts.json`
  73. Output:
  74. - final slide images saved sequentially into the workspace, for example:
  75. - `page_1.png`
  76. - `page_2.png`
  77. - `page_3.png`
  78. This step is intentionally separate so generation can:
  79. - inspect each page one by one
  80. - preserve deck consistency across outputs
  81. - save project-bound assets explicitly instead of leaving them in tool cache
  82. [Back to top](#future-slide-skill)
  83. ## Tightened Slide HTML decks
  84. `tightened-slide` is an independent HTML deck workflow. Use it when the target is
  85. a polished horizontal-swipe presentation rather than generated page images.
  86. It produces:
  87. - `index.html` from `skills/tightened-slide/assets/template.html`
  88. - an adjacent `images/` folder for local deck assets
  89. - a browser-ready presentation with keyboard navigation and static mode
  90. The skill is intentionally stricter than the general HTML slide workflow:
  91. - body slides must use the registered `S01` to `S22` layouts
  92. - maps and route/location pages should use `S08` with the Tightened Map Component
  93. - images must be assigned to known layout slots before prompting or placement
  94. - deck language is set explicitly with `lang` and `data-language`
  95. - delivery requires `node skills/tightened-slide/scripts/validate-deck.mjs path/to/index.html`
  96. Example:
  97. ```text
  98. $tightened-slide
  99. Create a 9-page Korean launch deck for a new AI research product.
  100. Use the International Klein Blue theme, include one hero image page, and validate the final HTML.
  101. ```
  102. [Back to top](#future-slide-skill)
  103. ## Example prompts
  104. Below are concrete example prompts based on the actual way these skills were used for the Samsung Biologics / Hana Securities workflow.
  105. ### `slide-design`
  106. Use when you have a reference slide image or reference deck image and want to extract a reusable design system.
  107. Example:
  108. ```text
  109. $slide-design [Image #1]
  110. ```
  111. More explicit example:
  112. ```text
  113. $slide-design
  114. Extract the design theme from this reference slide image.
  115. Focus on official DESIGN.md output with layout placement, header/body/footer flow,
  116. title page / body page / end page flow, icon usage, infographic cards, and diagram behavior.
  117. ```
  118. ### `gpt-image-slide-plan`
  119. Use when you already have `DESIGN.md` and want to build the storyline and slide sequence from files plus user intent.
  120. Example:
  121. ```text
  122. $gpt-image-slide-plan /Users/tonylee/Downloads/하나증권 _보고서.pdf
  123. Write the analysis slide for 'Samsung Biologics' in Korean based on report pdf file.
  124. ```
  125. Expanded full-deck example:
  126. ```text
  127. $gpt-image-slide-plan /Users/tonylee/Downloads/하나증권 _보고서.pdf
  128. Create a more detailed full deck in Korean from this equity research report.
  129. Keep the structure analytical and report-native.
  130. Plan title page, body pages, end page, and appendix/disclosure flow.
  131. ```
  132. ### `gpt-image-slide-prompt`
  133. Use after planning is complete and you want detailed page-level prompt JSON for slide generation.
  134. Minimal example:
  135. ```text
  136. $gpt-image-slide-prompt
  137. ```
  138. More explicit example:
  139. ```text
  140. $gpt-image-slide-prompt
  141. Use the current DESIGN.md and slide_plan.json.
  142. Generate strict page-by-page prompt JSON with explicit header/body/footer zoning,
  143. table/chart/card hierarchy, icon rules, and anti-generic constraints.
  144. ```
  145. ### `gpt-image-slide-render`
  146. Use after `slide_prompts.json` exists and you want actual slide images rendered sequentially.
  147. Minimal example:
  148. ```text
  149. $gpt-image-slide-render
  150. ```
  151. More explicit example:
  152. ```text
  153. $gpt-image-slide-render
  154. Based on @slide_prompts.json, create all slide images 1 by 1 and save them
  155. with the page_number naming rule.
  156. ```
  157. Full-deck example:
  158. ```text
  159. $gpt-image-slide-render
  160. Use DESIGN.md and slide_prompts.json.
  161. Render the full deck sequentially and save:
  162. page_1.png ... page_N.png
  163. ```
  164. [Back to top](#future-slide-skill)
  165. ## Example end-to-end usage
  166. Typical sequence:
  167. ```text
  168. $slide-design [reference slide image]
  169. $gpt-image-slide-plan /path/to/report.pdf Create a full Korean research-summary deck.
  170. $gpt-image-slide-prompt
  171. $gpt-image-slide-render
  172. ```
  173. ## What this bundle optimizes for
  174. - theme extraction first, content second
  175. - strong cross-slide consistency
  176. - persuasive story flow
  177. - explicit evidence-to-slide mapping
  178. - reusable layout families
  179. - body-slide discipline
  180. - title / body / end-page flow discipline
  181. - explicit header / body / footer zoning
  182. - icon / infographic / table / chart role clarity
  183. - sequential image generation with stable numbering
  184. - no hallucinated design rules when the reference image is ambiguous
  185. ## Output artifacts
  186. This bundle includes:
  187. - `skills/slide-design/SKILL.md`
  188. - `skills/gpt-image-slide/SKILL.md`
  189. - `skills/gpt-image-slide-plan/SKILL.md`
  190. - `skills/gpt-image-slide-prompt/SKILL.md`
  191. - `skills/gpt-image-slide-render/SKILL.md`
  192. - `skills/tightened-slide/SKILL.md`
  193. - `templates/DESIGN_TEMPLATE.md`
  194. ## Current skill responsibilities
  195. ### `slide-design`
  196. - extracts design theme, placement rules, header/body/footer flow, title/body/end-page behavior
  197. - captures icon usage, infographic card logic, table/chart treatment, and diagram behavior
  198. ### `gpt-image-slide-plan`
  199. - builds the storyline and page-family rhythm
  200. - decides where tables, charts, icon-led modules, or comparison exhibits belong
  201. - plans split topics across multiple pages when needed
  202. ### `gpt-image-slide-prompt`
  203. - converts the plan into strict per-page prompt JSON
  204. - makes layout family, zoning, and anti-generic rules explicit for every page
  205. ### `gpt-image-slide-render`
  206. - reads `DESIGN.md` and prompt JSON
  207. - renders slide images one by one with Codex native image generation
  208. - saves final outputs into the project using page-number naming
  209. ## Recommended generated artifact set
  210. For a full run, the typical artifact chain is:
  211. 1. `DESIGN.md`
  212. 2. `slide_plan.json`
  213. 3. `slide_prompts.json`
  214. 4. `page_1.png ... page_N.png`
  215. [Back to top](#future-slide-skill)
  216. ## Installation
  217. ### Install with `npx skills`
  218. Use the Skills CLI from a terminal with Node.js 18+:
  219. ```bash
  220. npx skills add jyoung105/future-slide-skill
  221. ```
  222. You can also use the repository URL:
  223. ```bash
  224. npx skills add https://github.com/jyoung105/future-slide-skill.git
  225. ```
  226. Restart Codex after installation so the new skills are discovered.
  227. ### Manual install into `.codex`
  228. Download or clone this repository, then copy the skill folders into your
  229. Codex skills directory:
  230. ```bash
  231. mkdir -p ~/.codex/skills
  232. cp -R skills/slide-design ~/.codex/skills/
  233. cp -R skills/gpt-image-slide ~/.codex/skills/
  234. cp -R skills/gpt-image-slide-plan ~/.codex/skills/
  235. cp -R skills/gpt-image-slide-prompt ~/.codex/skills/
  236. cp -R skills/gpt-image-slide-render ~/.codex/skills/
  237. cp -R skills/tightened-slide ~/.codex/skills/
  238. ```
  239. For project-local installation, copy the same folders into:
  240. ```text
  241. .codex/skills/
  242. ```
  243. Codex discovers skills from folders that contain `SKILL.md`, so each copied
  244. folder must keep its `SKILL.md` at the folder root.
  245. [Back to top](#future-slide-skill)
  246. ## License
  247. Future Slide Skill is released under the [Apache License 2.0](./LICENSE).
  248. [Back to top](#future-slide-skill)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.