Загрузка видео...

Не удалось загрузить видео

На главную

Built a vibe-coded presentation app generator that turns natural language into polished slides ✨ This project by Jerry Liu combines the Claude Agent SDK with LlamaParse to create an AI-powered presentation tool that handles everything from content creation to PDF export: 🎯 Chat-based slide creation - just describe what...

50,184 просмотров • 8 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

Nityesh

70,086 просмотров • 3 месяцев назад

I just built a branded IG carousel generator in Claude Code 🤯 One brand URL + one product name = 6 finished carousel slides. The kind an agency charges $2K to produce. All inside Claude Code. Perfect for DTC brands and agencies who need to post carousels every week but can't turn each one into a two-day design project. If every carousel is the same mini-project — writing the copy in Notion, rebuilding the template in Canva, exporting slides one at a time, then three rounds of revisions with your designer before it's even live... This tool eliminates the entire loop: → Drop in a brand URL and product name → Claude scrapes the site and extracts colors, fonts, voice, and positioning → Generates 6 slide concepts across proven carousel frameworks → Writes a detailed image prompt for each slide → Fires all 6 to ChatGPT Images 2.0 via FAL in parallel → Downloads finished slides + opens an HTML gallery No Canva. No designer back-and-forth. No generic AI slop. What you get: → Finished 1080x1350px slides ready to post directly to Instagram → Wavy color-blocked backgrounds, bold typography, product hero — all baked into the image → Brand-accurate colors and copy pulled from the live site automatically → A reusable pipeline — new brand, new folder, same 3-minute workflow Built 100% in Claude Code. I put together the full step-by-step playbook so you can build this yourself. Want it for free? Like this post Comment "SLIDES" And I'll send it over (must be following so I can DM)

Mike Futia

36,550 просмотров • 3 месяцев назад

The latest RAG trend for the current agent harnesses (Codex, Cowork) is to do two passes of document processing to solve a knowledge work task over a data room of documents: 1️⃣ A fast and light pass, oftentimes using a free/OSS doc parsing tool. This can be cheaply run across 10-100-1k’s of files, and enables the agent to then do retrieval (e.g. grep, semantic) to find relevant subsets of context. 2️⃣ A “just-in-time” VLM-based pass. Once the agent finds the relevant pages of context, it will screenshot the documents can call its own VLM (or write code) to dissect the pages. The issue with only using VLM-based OCR tools over massive ad-hoc customer file dumps is that it’s slow and expensive. Doing JIT VLM OCR allows the agent to filter through the data cheaply, but still preserve accuracy for the context that’s needed for the task. The agent harnesses do two-pass document processing by default using off the shelf-tools: pdf2text as the first pass, and using itself (Opus 5) as the second pass. See the below video where Cowork runs over a bunch of PDFs to answer a question about a benchmark graph in the Kimi k3 paper. The main issues here with the “out of the box” doc processing these agents offer are: * Opus 5 is not the best VLM for OCR. It is also way too expensive at scale and lacks grounding * The OSS tools like pypdf, pdf2text, may not be versatile enough as the first pass. * The agent will write a lot of throwaway code to rewrite things an OCR tool would’ve provided out of the box, like chart processing, bounding boxes, confidence scores, leading to increased cost and speed. We have all the tools within LlamaIndex 🦙 to help any agent do two-pass document processing with higher accuracy and lower cost. 1️⃣ We have liteparse for the first pass - a free/OSS parser written in Rust that’s faster/more accurate than other OSS parsers, and supports 50+ document types 2️⃣ We have LlamaParse for the second pass - an agentic document engine that uses VLMs+harnesses to achieve SOTA in accuracy and cost across various doc parsing and extraction tasks. It can be called from any agent harness as an MCP or skill. It takes in page numbers as input, so that the agent can choose to run LlamaParse over a subset of the doc instead of the full doc as a “zoom-in” pass. Come check it out! LiteParse: LlamaParse: All the relevant docs, including MCP, are here:

Jerry Liu

23,239 просмотров • 1 месяц назад

I think we're about to stop editing videos. Not because AI edits faster. Because it's starting to understand what you're trying to say. I think we're about to stop editing videos. Not because AI edits faster. Because it's starting to understand what you're trying to say. I found a tool called Pexo. I found a tool called Pexo. I used it to create a 45-second collage animation of two pugs climbing Mount Fuji. Think of it as a playful concept for a pet travel brand. Instead of opening a timeline and dragging clips around, you give it a URL, document, or source material and tell it what you want. Then you talk to it. It builds the video. Instead of opening a timeline and dragging clips around, you give it a URL, document, or source material and tell it what you want. Then you talk to it. It builds the video. If you want changes, you don't re-edit the timeline. You just ask. That's the interesting part. If you want changes, you don't re-edit the timeline. You just ask. That's the interesting part. • Turn URLs into videos • Use docs or source material as input • Refine videos through conversation • No editing experience required • Built for product launches, explainers, and brand content • Keep iterating until it's ready to publish • Turn URLs into videos • Use docs or source material as input • Refine videos through conversation • No editing experience required • Built for product launches, explainers, and brand content • Keep iterating until it's ready to publish We're moving from editing videos to directing AI. That feels like a much bigger shift than most people realize. We're moving from editing videos to directing AI. That feels like a much bigger shift than most people realize. Get free credit by using this code: B4QFWK Try Pexo here:

Hasan Toor

174,034 просмотров • 27 дней назад