codebase-slide-deck

Create technical slide decks from codebase architecture, flows, and implementation evidence.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tarabakz25/my-skills --skill codebase-slide-deck-tarabakz25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-slide-deck
Source: https://github.com/tarabakz25/my-skills/tree/main/codebase-slide-deck
Command: npx skills add https://github.com/tarabakz25/my-skills --skill codebase-slide-deck-tarabakz25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a codebase into a clear technical presentation requires hours of manual investigation and slide drafting. This Skill inspects repository structure, flows, modules, APIs, and tests, then converts verified findings into a slide outline and editable PPTX deck. ## Core Features & Use Cases - Evidence-Based Investigation: Maps entry points, architecture, data models, flows, tests, and operations with traceable file-path references before drafting any slide. - Deck Type Patterns: Supports architecture overviews, onboarding walkthroughs, feature deep dives, refactor proposals, and incident explanations with slide-by-slide specs. - PPTX Export via Presentations: Hands off narrative, slide specs, and evidence to the Presentations skill for authoring, export, and rendered visual QA. - Use Case: A new engineer joins your team. Point the Skill at your repository and request an onboarding deck; it inspects the code, drafts slide specs with evidence paths, and produces an editable PowerPoint walkthrough. ## Quick Start Use the codebase-slide-deck skill to create an architecture overview presentation from this repository.

Frequently Asked Questions about codebase-slide-deck

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

FAQPage Schema
How do I create a slide deck from a codebase?▼

Request a deck and specify the audience, purpose, and slide count if known. The skill inspects entry points, modules, schemas, and tests, builds an evidence map with file paths, drafts slide specs, then exports an editable PPTX through the Presentations workflow.

What types of technical presentations can be generated from a repository?▼

Five deck types are supported: architecture overview, onboarding walkthrough, feature deep dive, design or refactor proposal, and incident or bug explanation. Each follows a defined slide structure in the deck patterns reference.

Can I generate Japanese slide decks from code?▼

Yes, Japanese decks are supported, including requests like コードベースからスライド資料を作成 or 技術説明資料. Slide text uses short noun phrases, code terms stay as-is, and long explanations go into speaker notes.

Does the skill produce an actual PowerPoint file?▼

Yes, when a PPTX is required it invokes the Presentations skill after slide specs are ready, passing the narrative, evidence, and brand constraints. Output includes the editable .pptx path plus preview renders and verification notes.

How does the skill avoid inventing architecture details?▼

Every slide claim must trace to a file path, code, docs, or tests, and uncertain behavior is marked as inferred. README claims are verified against actual code paths, and the finished deck is re-checked against repository facts.

When should I not use codebase-to-slides generation?▼

Avoid it when you only need a file tree dump or raw documentation export, since the skill organizes around decisions and flows rather than exhaustive listings. For very large repositories, investigation samples strategically from manifests and entry points.