slides

Render 16:9 slide decks from code-based components and a manifest.

2|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/tamnguyentommy-rgb/Routex_AI_Web_Project --skill slides-tamnguyentommy-rgb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slides
Source: https://github.com/tamnguyentommy-rgb/Routex_AI_Web_Project/tree/main/.local/skills/slides
Command: npx skills add https://github.com/tamnguyentommy-rgb/Routex_AI_Web_Project --skill slides-tamnguyentommy-rgb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to programmatically assemble, edit, and deploy presentation decks by placing slide components and a manifest in a workspace, ensuring consistent 16:9 visuals from code.

Core Features & Use Cases

  • Manifest-driven deck rendering: A single source of truth for slide ordering, titles, and speaker notes.
  • 1:1 PPTX import workflow: Seamless import of PowerPoint files into code-generated slides with fidelity-preserving components.
  • Extensible artifact access: Optional directories for scripts, references, and assets to support data, media, and tooling.
  • Design-guided, production-ready decks for presentations, pitches, and classroom materials.

Quick Start

Place your slides under the slides artifact and run the build to generate the deck.

Frequently Asked Questions about slides

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a 16:9 presentation deck from code?

To generate a presentation deck from code, you place your slide components and a manifest file in the workspace and run the build process. This organizes and renders production-grade 16:9 slides programmatically.

Can I import a PPTX file into code-generated slides?

Yes, you can import PPTX files into code-generated slides using a 1:1 import workflow. This process converts PowerPoint files into fidelity-preserving, code-based slide components within your deck.

What is a manifest-driven deck rendering workflow?

Manifest-driven deck rendering uses a single manifest file as the source of truth for slide ordering, titles, descriptions, and speaker notes. It ensures consistent 16:9 visuals across your presentation deck.

Do I need React to build code-driven slide decks?

Code-driven slide decks support React workflows to assemble and edit presentation components programmatically. You organize slide files and a manifest to deploy production-ready decks for pitches or classroom materials.

What are the limitations of automated deck validation?

Automated deck validation requires strict adherence to a YAML frontmatter schema on SKILL.md files, mandating specific name and description fields. The manifest schema also strictly governs slide file paths, titles, and speaker notes.

How do I manage scripts and media assets for a presentation deck?

You manage scripts, references, and media assets by placing them in optional extensible artifact directories within the workspace. This supports data, media, and tooling alongside your code-based slide components and manifest.