infographic-powerpoint-deck
Infographic PowerPoint Deck
Default input model (raw article first)
This skill should work directly from the user's raw article content by default.
If the user provides a full article, sermon, report, or long notes:
- Read the source content and infer the audience, burden, density, and argument/story structure.
- Build
slides_message_plan.mdfrom the article structure. - Turn
slides_message_plan.mdintoslides_display_plan.md. - Turn
slides_display_plan.mdintoslides_visual_plan.md. - Write one image prompt per slide and generate the deck.
If the user already provides slides_message_plan.md or an equivalent content-first slide table, you can skip the article-intake step and use that directly.
If the user provides one or more reference slides/screenshots, use references/reference_slide_intake.md to extract the reusable visual grammar before writing prompts.
Artifact model
More from autobyteus/autobyteus-skills
product-ui-prototyping
Design and validate product UI behavior as visual state prototypes before coding. Use when tasks ask how screens should change after user actions (click, tap, submit), when non-developers need to review web/iOS/Android UX flows, or when teams need interaction-state assets and acceptance checks for implementation.
61software-engineering-workflow-skill
Run a staged software-engineering delivery feedback loop from bootstrap through investigation, requirements, design, runtime review, implementation, API/E2E and executable validation, code review, docs sync, and final handoff with durable artifacts and explicit re-entry.
55computer-use-playbook
Use when tasks involve cross-application computer use (browser, file explorer, and native dialogs) and require choosing between DOM, vision, shell, and native UI automation.
28deep-research-article
Do deep research and synthesize it into one logically structured article with clear thesis, argument flow, evidence, objections, and takeaways. By default, this skill requires internet source collection and deep reading before drafting. Use when the user wants a strong reasoning artifact first: sermon notes, Bible passage study, policy/tech explainers, product narratives, or any topic where downstream artifacts should start from an approved article.
24ux-journey-definition
Define a practical, story-first product experience before UI prototyping. Use when you need one canonical artifact that explains what users see, what they can do, and how screens transition.
19emotion-metaphor-image-prompting
Craft and iteratively refine image-generation and image-edit prompts that turn subtle feelings, idioms, pressure, or social dynamics into concrete visual metaphors. Use when a user can describe the emotion but not the picture yet, when a generated image is close but not exact, or when Codex needs to preserve style while correcting one visible signal at a time.
3