Turn a README into conference or demo slides
A README explains how a project works. A presentation explains why the audience should care, what changed, and which evidence supports the conclusion. TweakSlides gives an agent or developer a source-first way to make that translation.
Choose authoritative files
Start with the README, architecture decisions, roadmap, and verified metrics—not the entire repository.
Name the audience
A conference talk, engineering review, and product launch need different levels of implementation detail.
Review the technical claims
Keep filenames or source labels beside important claims, then refine the deck in Markdown.
Audience: platform engineers. Sources: README.md and docs/architecture.md. Focus: why optimistic versioning prevents agent overwrites. Eight slides, one diagram, no invented benchmarks.
A technical narrative grounded in the chosen files, with a process diagram, trade-off slide, and reviewable Markdown source.
Documentation is evidence, not the narrative
README sections often follow installation order: requirements, setup, commands, configuration, and troubleshooting. A talk usually needs a different arc: problem, constraint, idea, architecture, proof, trade-offs, and next step.
The source files keep the deck grounded. The presentation layer decides what the audience needs to understand.
Preserve what technical audiences inspect
Use code only when the exact syntax matters. Prefer a process diagram for flow, a comparison for trade-offs, and a chart for measured results. Keep caveats and unsupported assumptions visible.
- Architecture and data flow
- Measured outcomes with source labels
- Constraints and rejected alternatives
- Demo sequence and next steps
Let Codex or Claude Code prepare the first pass
An agent can read the selected repository files and submit a TweakSlides proposal without changing the project. The human then edits the narrative and visual emphasis in the browser.
What it does not do yet
- The tool does not automatically verify whether documentation is current.
- Repository secrets and private source must not be pasted into public tools.
- Complex live demos still need rehearsal outside the slide deck.
Questions, answered plainly
Can TweakSlides render code and diagrams?
Yes. It supports fenced code, Mermaid diagrams, tables, math, and presentation-oriented layouts.
Does the agent need write access to my repository?
No. A proposal-only workflow can read the selected context and submit the deck without modifying repository files.
Can I export the final talk?
Yes. Current export paths include PDF, standalone HTML, and Markdown source.