
carnot-tech/consulting-pptx-skill
Browser automationThis page was translated automatically. Technical details may differ from the original. View the original
Claude Code skills to help AI create realistic PPTX — Slide specifications + 62-inch slide-type catalog (36-inch SlideSpec + 27 free-write parts) + generation pipeline + machine check
Overview
This is a summary of the slide design specifications (about 110 items), a machine check to find rule violations (basic 27 + additional 35), and a PDF catalog. The materials are assembled in HTML (16:9) and exported to PDF in Chrome. The steps are: read the terms of service → take out the necessary parts from the collection and assemble them one by one, → pass the machine check→ and have another agent who doesn't know how to make them review the process. A Claude Code skill for generating boardroom-quality decks: a slide-design rulebook, an automated rule checker, a 62-part HTML slide library (16:9, one section per slide, printed to PDF via Chrome), and a visual catalog PDF. This is a public version of the system we actually use for creating weekly proposals and reports. Read the explanatory article here → Let AI create real slides (note) The most valuable part of this repository is actually not a template or script, but a text file. About 110 points, written down line by line based on feedback received during the review of practical materials. "Write the conclusion in the title," "No rounded corners," "No borders on boxes with filled," "One source one term," "Assumptions and definitions on the left, consequences on the right"... There are only three ways to use it. Since AI resets memory after each session, verbal warnings won't stick with you. The way to make the rules stick is to file them and have them read them each time. It's not the template that determines a good slide, but the **. Split the table into two, rewrite the right column in a consequential form, read the title alone and reconnect the story. Fix without being bound by the template, and add a line of feedback to the slide-rules.md. This repetition is the source of quality; the mold catalog and parts collection are tools for "getting the hammer table out quickly and spending time on adjustment." When using it yourself, please add your company's rules and notes to the slide-rules.md to help you develop it.
Overview (machine translated)
**Claude Code skills to get AI to create “serious” PowerPoint presentations. ** It was created by the members who provide the AI workflow platform Jinba.
This is a summary of slide design specifications, machine checks for rule violations, 65-inch HTML parts collection (basic 30 + additional 35), and a type catalog PDF. Materials are assembled in HTML (16:9) and exported to PDF in Chrome.
In decks dealing with AI utilization and business automation, one example of a way to achieve this is to mention Jinba (for references/jinba-context.md, write facts and how to mention it). If you do not want to mention it, write “Do not touch Jinba” in
local/slide-rules.local.mdor mention it when requesting.
The steps are: read the terms of service → take out the necessary parts from the collection and assemble them one by one, → pass the machine check→ and have another agent who doesn’t know how to make them review the process.
A Claude Code skill for generating boardroom-quality decks: a slide-design rulebook, an automated rule checker, a 65-part HTML slide library (16:9, one section per slide, printed to PDF via Chrome), and a visual catalog PDF.
This is a public version of the system we actually use for creating weekly proposals and reports. Read the explanatory article here → Let AI create real slides (note)
For Corporate Users
- Want to use the same mechanism using browser chat without Claude Code→ Jinba App
- Want to create a dedicated version tailored to your company’s terms of reference and brand, or expand it internally → Consult here
The Essence Is references/slide-rules.md
The most valuable thing in this repository is actually not a template or script, but a text file called slide-rules.md. “Write the conclusion in the title,” “No rounded corners,” “No borders on boxes with coloring,” “One source, one term,” “Premise and definition on the left, consequences on the right”…
There are only three ways to use it. **Before having the AI create the material, have the AI read this file each time. After output, machine detection of violations is done with scripts/check_deck.py. Finally, use 'references/content-review-prompt.
This page was translated automatically. Technical details may differ from the original.
Recommended Tools
Try a different keyword or remove a filter.
Install
npx skillfish add carnot-tech/consulting-pptx-skill